column_values of the mutations support objects in addition to
JSON strings? The objects would be the underlying types the JSON deserializes to.
This way the schema would actually expose this structure, so those of us using GraphQL tooling that utilizes the schema (such as turn it into TypeScript types) can type check what we’re doing, and create validators for the query data.
I realized this may force the use of variables - something I am actually in favor of. JSON strings just encourage novice devs to try to construct mutations as strings, and struggle with properly escaping everything. Its just a poor practice in my opinion.