I noticed that the current implementation assumes root level queries query and mutation (I think?). Please note that while this probably how most people are using graphql, modeller shouldn't make any assumptions about user top level queries.
A top level query can have the following example forms (Again, I'm pretty sure this is how it works):
query Alias {}
someThing Thingie {}
mutation lol {}
Users should be able to specify the top level exposed name and the specific query alias. Also, mutations are functionally equivalent to queries. The only difference is convention.
I noticed that the current implementation assumes root level queries
query
andmutation
(I think?). Please note that while this probably how most people are using graphql, modeller shouldn't make any assumptions about user top level queries.A top level query can have the following example forms (Again, I'm pretty sure this is how it works):
Users should be able to specify the top level exposed name and the specific query alias. Also, mutations are functionally equivalent to queries. The only difference is convention.