Support using Input Types for Mutation arguments

[prisma]

Support using Input Types for Mutation arguments

[sorenbs]

This is happening :-) Thanks for the great suggestion! https://github.com/graphcool/framework/issues/353

[ThisIsMissEm]

👍 to being able to select which mutations and queries are exposed. This would be a great feature

[ThisIsMissEm]

This is inspired by this example in the GraphQL Documentation:

[schickling]

Would be using the Relay API an option for you as well?

[ThisIsMissEm]

Maybe, but it greatly complicates things. I'd say using Input Types is a general great practice that should be encouraged.

[schickling]

There are a couple of alternatives from the top of my head:

1. Embed the input type into existing mutations. The upside would be that you could choose between providing a "combined object" matching input type vs spreading out all fields directly. The big downside of this approach is that all arguments would need to be optional (non-required). That means we'd lose a lot of the type system's power along the way.

2. An alternative approach would be to generate additional mutations like createPostWrapped(post: { ... }. The upside of this would be that it preserves the expressiveness of the typesystem. But obviously this approach would clutter the query namespace quite a lot. (This could be solve though by selectively configuring which queries should be exposed in the schema at all).

3. A third approach would be to make it a configuration option on a project basis which "layout" of mutations you'd prefer. This could however confuse people quite a bit.

Would be interested to hear what your thoughts are on this and especially if you'd see any other viable options?

[ThisIsMissEm]

I'd say a configuration option, perhaps per model, would be best.

[ThisIsMissEm]

But also, new projects should be created in the input type mode, and allow you to switch if you want.

[marktani]

We're looking to enhance the Simple API with an object input argument as described in this feature request. This would be a great opportunity to work on other feature requests that require an input object, like #45.