Fix SubgraphServiceError to return JSON-formatted error responses #652
Conversation
This file contains 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
neithanmo
force-pushed
the
fix/subgraph_service_error
branch
from
1e14ad0 to
54571c2
Compare
Pull Request Test Coverage Report for Build 13846533883Details
💛 - Coveralls |
suchapalaver
approved these changes
Mar 13, 2025
TypeLevelConsoli
approved these changes
Mar 13, 2025
neithanmo
force-pushed
the
fix/subgraph_service_error
branch
from
54571c2 to
88967fa
Compare
carlosvdr
approved these changes
Mar 14, 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.
Updates the SubgraphServiceError implementation to return proper JSON-formatted responses, consistent with IndexerServiceError. This fixes JSON parsing errors in GraphQL clients when handling error cases, for example introspection queries