You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more a comment / to provoke discussion rather than an issue but I just wasn't sure where to put it.
I've been looking at GraphQL for a little over a week now and having spent some time looking at how schemas are declared/defined in different implementations it strikes me that some are much easier to read and understand than others. For instance the Javascript examples provided by FB are very easy to read and understand but the corresponding Java implementation is much more difficult to read.
Now I have nothing against GraphQL-Java, in fact I plan on using this for a demonstration project within my organisation, but the complexity of reading the schema generation code led me to think that in an ideal world there would be a single way to define a schema and and it's constituent components. A GraphQL DSL, if you like, and have a common file type to save these into.
For arguments sake, the DSL could simply be Javascript but saved with an alternative file extension. I would be interest to know other peoples thoughts on this?
The text was updated successfully, but these errors were encountered:
andye2004
changed the title
Common file type for schemas?
Common DSL and file type for schema definitions?
Mar 12, 2016
This is more a comment / to provoke discussion rather than an issue but I just wasn't sure where to put it.
I've been looking at GraphQL for a little over a week now and having spent some time looking at how schemas are declared/defined in different implementations it strikes me that some are much easier to read and understand than others. For instance the Javascript examples provided by FB are very easy to read and understand but the corresponding Java implementation is much more difficult to read.
Now I have nothing against GraphQL-Java, in fact I plan on using this for a demonstration project within my organisation, but the complexity of reading the schema generation code led me to think that in an ideal world there would be a single way to define a schema and and it's constituent components. A GraphQL DSL, if you like, and have a common file type to save these into.
For arguments sake, the DSL could simply be Javascript but saved with an alternative file extension. I would be interest to know other peoples thoughts on this?
The text was updated successfully, but these errors were encountered: