We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Server Version: v2.35.1
OSS and EE
The update_<table>_many mutation response returns an object when the updates argument is an empty array
update_<table>_many
updates
It should always return an array as described by the GraphQL schema for consistency, i.e.
{ "data": { "update_users_many": [ { "affected_rows": 0 } ] } }
Invoke an update_<table>_many mutation, passing an empty array argument:
mutation { update_users_many(updates:[]) { affected_rows } }
See that it unexpectedly returns an object:
{ "data": { "update_users_many": { "affected_rows": 0 } } }
The current state requires awkward conditional logic in GraphQL client implementations
multiple updates, mutation, update_many
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Version Information
Server Version: v2.35.1
Environment
OSS and EE
What is the current behaviour?
The
update_<table>_many
mutation response returns an object when theupdates
argument is an empty arrayWhat is the expected behaviour?
It should always return an array as described by the GraphQL schema for consistency, i.e.
How to reproduce the issue?
Invoke an
update_<table>_many
mutation, passing an empty array argument:See that it unexpectedly returns an object:
Any possible solutions/workarounds you're aware of?
The current state requires awkward conditional logic in GraphQL client implementations
Keywords
multiple updates, mutation, update_many
The text was updated successfully, but these errors were encountered: