The auth/me functionality is already implemented at the backend level, but it is not currently exposed or usable within the frontend when using Auth Presets.
This limits developers from easily accessing the authenticated user's data (e.g., id, email) directly in frontend logic or form bindings.
Problem:
auth/me exists but is not accessible in the frontend layer.
Developers cannot directly retrieve logged-in user details after authentication.
Forces manual workarounds despite backend support already being present.
Proposed Solution:
Integrate and expose auth/me inside the frontend Auth Presets system:
Provide a frontend method:
postpipe.auth.me()
which internally calls the existing auth/me endpoint.
Store the response in a globally accessible state:
postpipe.auth.user
Enable direct usage in forms:
Example: hidden field auto-binding
Ensure this runs automatically after login (OAuth or other presets).
Expected Behavior:
After login, user data is instantly available on frontend.
No need for manual fetch or token handling.
Seamless integration with form submissions and UI logic.
Why This Matters:
Completes the auth flow by bridging backend → frontend.
Critical for building real systems (orders, dashboards, ownership tracking).
Improves developer experience by removing redundant steps.
Priority: High
Note:
Backend support for auth/me already exists — this issue is specifically for frontend exposure and integration within Auth Presets.
The auth/me functionality is already implemented at the backend level, but it is not currently exposed or usable within the frontend when using Auth Presets.
This limits developers from easily accessing the authenticated user's data (e.g., id, email) directly in frontend logic or form bindings.
Problem:
auth/me exists but is not accessible in the frontend layer.
Developers cannot directly retrieve logged-in user details after authentication.
Forces manual workarounds despite backend support already being present.
Proposed Solution:
Integrate and expose auth/me inside the frontend Auth Presets system:
Provide a frontend method:
postpipe.auth.me()
which internally calls the existing auth/me endpoint.
Store the response in a globally accessible state:
postpipe.auth.user
Enable direct usage in forms:
Example: hidden field auto-binding
Ensure this runs automatically after login (OAuth or other presets).Expected Behavior:
After login, user data is instantly available on frontend.
No need for manual fetch or token handling.
Seamless integration with form submissions and UI logic.
Why This Matters:
Completes the auth flow by bridging backend → frontend.
Critical for building real systems (orders, dashboards, ownership tracking).
Improves developer experience by removing redundant steps.
Priority: High
Note:
Backend support for auth/me already exists — this issue is specifically for frontend exposure and integration within Auth Presets.