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 allows fields to have a
graphql
reflect tag in order to override the name of the field they resolve. This in turn would allow for field resolvers which are case-sensitive. Currently the library matches fields using case-insensitive matching and the_
char is insignificant. This violates the official GraphQL spec which states that names should be case-sensitive and the_
is significant.With this change, similar to the
json
reflect tag, users can set agraphql
tag in order to override the name. For example:or
The above would allow the users to override the name and use a case-sensitive matching. Both of the above resolvers would resolve a schema like this:
fixes: #593