adding support for the id scalar constrained as a string #205
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
|
Thanks @mrcarolin for this. Can you add some test cases? |
Pull Request Test Coverage Report for Build 7268837238
💛 - Coveralls |
|
ok will do, ty |
|
@confuser updated with a couple tests showing how ID is treated just like string now |
|
@confuser Thank you for merging - if possible could a new release be created with this change? |
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 will allow custom format on the ID scalar.
export declare const GraphQLString: GraphQLScalarType<string, string>; export declare const GraphQLID: GraphQLScalarType<string, string>;