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.

Sign up for GitHub

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

Jump to bottom

Input of GraphQL update mutations should be non-nullable #449

Open
szakhlypa opened this issue Feb 19, 2024 · 0 comments
Open

Input of GraphQL update mutations should be non-nullable #449

szakhlypa opened this issue Feb 19, 2024 · 0 comments
Labels
ash-porting Issues used to track open issues regarding the Ash porting process

Comments

@szakhlypa
Copy link
Contributor

Since we expect to update the resource with the update mutation, there is no reason to allow null as an input.
@szakhlypa szakhlypa added the ash-porting Issues used to track open issues regarding the Ash porting process label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ash-porting Issues used to track open issues regarding the Ash porting process
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@szakhlypa