Clerk middleware for resolvers working #102
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goal: Improve security and get the graph ql resolvers working again
clerkMiddleware()
) for user verification via JWT, so no more manual auth middlewaregetUserFromHeaders
decodes the JWT from request headers to verify the user in each resolver, helps readability and decreases LOCuserID
from decoded JWT ensures that each request is tied to the authenticated userdecodedToken.sub
for filtering data specific to the authenticated user, rather than the old code usingargs.userID
directly