perf(graphql): use depth 0 in auth/apiKey for graphQL requests#13895
Merged
DanRibbens merged 2 commits intopayloadcms:mainfrom Sep 24, 2025
Merged
perf(graphql): use depth 0 in auth/apiKey for graphQL requests#13895DanRibbens merged 2 commits intopayloadcms:mainfrom
DanRibbens merged 2 commits intopayloadcms:mainfrom
Conversation
rjgtav
changed the title
rjgtav
force-pushed
the
rjgtav/perf-auth-apikey
branch
from
f237939 to
42c3825
Compare
DanRibbens
approved these changes
Sep 24, 2025
Contributor
|
Thanks @rjgtav! |
Contributor
|
🚀 This is included in version v3.57.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What?
Sets depth to 0 when finding the corresponding user in auth/apiKey.
This matches the current behavior of auth/jwt
Why?
Optimizes the authentication step by making just one database query instead of two, when using sessions. Particularly impactful when there's latency between Payload and the database
How?
By leveraging the already existing isGraphQL flag of the AuthStrategyFunction