Description
Right now, the update_group mutation only allows specifying one group attribute at a time.
While GraphQL supports chaining aliasing to chain multiple calls together, that solution is only practical when the fields are known in advance or hardcoded.
What are you trying to achieve
In backend workflows (like BPMN style automation), mutations are often dynamically generated based on optional user input from a UI. For example: Some users may only want to update the group title, some may want to change colour and position, others might want to update all three.
Because of this, generating aliased mutations for every possible combination becomes unnecessarily complex and error prone - especially when the data is dynamic and passed from a frontend form.
PROPOSED SOLUTION
Allow update_group to accept multiple OPTIONAL attributes in a single update_group mutation: