Reject enum literals for custom scalar values #86
+37
−0
Conversation
This file contains hidden or 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
Enum literal values were being allowed and then coerced to Ruby strings in bluejay-rb. They should be rejected during validation up front.
swalkinshaw
force-pushed
the
fix-enum-literals-validation-issue
branch
from
040fdde to
cdb6882
Compare
Contributor
Author
|
We'll implement this in bluejay-rb instead since that's the only place where we have a need for this so far. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Enum literal values were being allowed and then coerced to Ruby strings in bluejay-rb. They should be rejected during validation up front.