Support IResult via GraphQLExecutionHttpResult for .NET 6+ #1191
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
tests/Transports.AspNetCore.Tests/ExecutionResultHttpResultTests.cs
Dismissed
Show dismissed
Hide dismissed
gao-artur
approved these changes
Jul 14, 2025
This was referenced Jul 29, 2025
Closed
Closed
This was referenced Aug 6, 2025
Closed
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.
This PR adds
ExecutionResultHttpResultandGraphQLExecutionHttpResultto mirror the functionality ofExecutionResultActionResultandGraphQLExecutionActionResult, providingIResultimplementations versusIActionResultimplementations.IResultis for route handlers (MapGet/MapPost/ etc) in .NET 6+ minimal APIs, whereasIActionResultis for MVC controller actions. Documentation has been updated; sample project added; tests added. No breaking changes.Feature added based on request/discussion within: