Fix NodePattern for fields without a name #20
Merged
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
`field` can be called without a position name argument which causes errors right now. This also happens when FieldExtension's are used; methods are called on `field` instead of passing arguments. The simplest fix was to ensure the node pattern matching for field definitions required a symbol positional argument (the field name).
DmitryTsepelev
approved these changes
Jul 21, 2020
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.
fieldcan be called without a position name argument which causes errors right now. This also happens when FieldExtension's are used; methods are called onfieldinstead of passing arguments.The simplest fix was to ensure the node pattern matching for field definitions required a symbol positional argument (the field name).