docs(graphql): registration order and what happens when it is wrong - #132
Merged
Conversation
AddTraxGraphQL() picks its subscription interceptor from the auth schemes registered by the time it runs, so authentication has to be registered before it. That was true before and undocumented; the difference now is that the wrong order fails at startup instead of quietly accepting every connection_init. Also says plainly what is not order-dependent, since that is the more common question: @authorize is on the schema, so query and mutation gating works either way round. Adds reference/registration-order.md as the tracked home for the contributor rule. The workspace CLAUDE.md is not in any repo, so guidance that only lives there does not reach CI or another clone.
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.
AddTraxGraphQL() picks its subscription interceptor from the auth schemes registered by the time it runs, so authentication has to be registered before it. That was true before and undocumented; the difference now is that the wrong order fails at startup instead of quietly accepting every connection_init.
Also says plainly what is not order-dependent, since that is the more common question: @authorize is on the schema, so query and mutation gating works either way round.
Adds reference/registration-order.md as the tracked home for the contributor rule. The workspace CLAUDE.md is not in any repo, so guidance that only lives there does not reach CI or another clone.