[nullability] Allow to use @catch on field definitions
#48
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
BoD
approved these changes
Feb 14, 2024
| Parent positions can recover using `RESULT` or `NULL`. | ||
| If no parent position recovers, the parsing stops. | ||
| """ | ||
| THROW |
There was a problem hiding this comment.
Should we rename this to EXCEPTION while we're at it?
There was a problem hiding this comment.
I'm a bit hesitant because IIRC relay uses THROW. That's something we certainly want to bikeshed and until we do, i'd just keep the current naming to avoid too much back & forth
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.
Allow to use
@catchon field definitions:And for type extensions:
See #47