fix validate_session query selection set#9
Open
localnerve wants to merge 1 commit intoauthorizerdev:mainfrom
Open
fix validate_session query selection set#9localnerve wants to merge 1 commit intoauthorizerdev:mainfrom
localnerve wants to merge 1 commit intoauthorizerdev:mainfrom
Conversation
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
1 participant
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.
Description
This PR fixes a GraphQL validation error in the ValidateSession method.
The Issue
The ValidateSession method was sending a GraphQL query that included the user field without a selection set: ... { validate_session(params: $data) { is_valid user } }
Because User is a composite object type in the Authorizer schema, the GraphQL specification requires an explicit selection of subfields. This caused the server to return the following error:
"Field 'user' of type 'User!' must have a selection of subfields. Did you mean "user { ... }"?"
The Fix
Updated validate_session.go to use fmt.Sprintf and the existing UserFragment (defined in common.go). This ensures the query now correctly requests the standardized set of user subfields, satisfying the GraphQL requirements and matching the implementation pattern used in the Login and SignUp methods.
Changes