Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@catch/@semanticNonNull Reword level description #41

Closed
wants to merge 2 commits into from
Closed

Conversation

martinbonnin
Copy link
Contributor

@martinbonnin martinbonnin requested a review from a team as a code owner January 12, 2024 10:51
@@ -32,7 +32,7 @@ The `field` argument is the name of the field if `@semanticNonNull` is applied t
If `@semanticNonNull` is applied to a field definition, `field` must be null.

The `level` argument can be used to indicate what level is semantically non null in case of lists.
`level` starts at 0 if there is no list. If `level` is null, all levels are semantically non null.
`level` is zero indexed. If `level` is null, all levels are semantically non null.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be worth clarifying what it means to use level on a non-list field. Is it an error? Is it ignored? Similarly, what about if it points to a level that does not exist?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added this in #42. Will close this PR in favor of #42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants