Jeff Ward

The following throws no errors, even though the parameter type does not exist. We should verify these parameter types (may be required to be input types? Do we support input...

Graphql requires: http://facebook.github.io/graphql/June2018/#sec-Names `/[_A-Za-z][_0-9A-Za-z]*/` For typedefs, Haxe requires: `/[_]?[A-Z][_0-9A-Za-z]*/`

Should catch typos / mismatches (and ideally "unused variables") in query variable names: ``` query FooQuery($some_id: ID!, $withBaz: Boolean!, $limit: Int) { foo_query(a: $some_typo_id, b: $limit_typo, c: $offset_typo) { bar...

hxgen: Support __typename in queries

1

Should be possible in any object type (though not fragments) 

Currently unsupported: http://facebook.github.io/graphql/June2018/#sec-Union-Extensions

Per this article: https://code.haxe.org/category/other/deploy-to-haxelib-using-travis-and-github-releases.html

Maybe? Or maybe just generate the function signatures? For callbacks and/or promises? Include a simple fetch client?

In the web demo, the left-hand (GraphQL) input isn't formatted, it's just plain black and white text.  Implement: https://github.com/graphql/codemirror-graphql - code highlighting - linter + typeahead

Let's talk about expanding beyond schema / Other Uses Cases

3

Right now these tools focus on using graphql merely as a schema / type description tool. For me, this is my primary use case -- generating Haxe type definitions from...

In the haxelib / macro workflow, the plan is to support automatic type creation based on inlined (or from file) schema. Something like this: