NET 10 Support | Sept '25 spec updates #172
Merged
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
finished input field validation on documents. Added new validation processor for comparing actual resolved variable data their usages before execution to allow for data checks for @OneOf
still need to update error message usages correctly.
confirmed the lexer supports arbitrary string placement..
added default fall back for deprecated reason
graphql-aspnet-owner
approved these changes
Dec 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
GraphQL Spec Sept '25 Updates
Major Updates
@oneOfdirective (see documentation for details)Bug Fixes
Solution Updates
.slnxformatgraphiql.htmleditor page so that it works again.Closes #171
Relates to: graphql-aspnet/graphql-aspnet.github.io#76