fix(hermes): named route response types handled as string responses #331
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
kon14
requested review from
kkopanidis,
sdimitris,
ChrisPdgn and
SotiriaSte
ChrisPdgn
approved these changes
Sep 19, 2022
kkopanidis
approved these changes
Sep 19, 2022
kon14
added a commit
that referenced
this pull request
Sep 22, 2022
Corresponding GraphQL fix in #331 (eyJhbG) only addressed Queries.
10 tasks
kkopanidis
pushed a commit
that referenced
this pull request
Sep 22, 2022
Corresponding GraphQL fix in #331 (eyJhbG) only addressed Queries.
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.
Fixes a bug where named route response types where handled as string responses.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
The PR fulfills these requirements:
mainbranchfix #xxx, where "xxx" is the issue number)