Any chance for a input union support?

[TheServerAsterisk]

Even though it is not officially supported by the current specs, there is currently an unofficial implementation for it. Personally, I think it would be great if it was there was perhaps a feature or is there a good workaround for this issue?

[mhallin]

Interesting. We could maybe support it with a feature flag. Are there any other GraphQL implementations that support it?

[TheServerAsterisk]

No, as far as I can tell there doesn't seem to be direct support for it in other implementation or even indirect support, but many of these are projects are quite young like this one.

There might of have been some indirect support for it in the Go implementation but overlooked it due to a lack of familiarity with the language (not likely though). While I have figured out a different way to approach the data, it just would have been nicer and less complex. I'll leave it up to you on what should be done.

[mhallin]

After thinking on this and working some more on an application, it seems as if a limited version of input unions that "automatically" maps to tagged Rust enums would be interesting. It would be a subset of the specification linked above.

I will try to work on this for a bit. The tricky part is to not build something that a later GraphQL will make obsolete :)

[theduke]

Le'ts not support anything not in the spec, we have enough catch-up work to do as is.

We can re-open if/when this gets accepted.