apollo-compiler 1.0 checklist

[lrlna]

Potential breaking API changes (to do before leaving beta, or decide not to do)

Beta Give feedback

1. compiler: should definitions know their own name? #708
   apollo-compiler +1
   
2. It’s too easy to use a schema or document with errors #709
   apollo-compiler +1
   
3. Make ast::Name a type wrapper that checks validity #710
   apollo-compiler +1
   
4. Diagnostic and Diagnostics are very similar names #711
   +0
   
5. represent parameterised grammar (const values) #538
   apollo-compiler apollo-parser bug +3
   

Tasks

Beta Give feedback

1. validation on top of current data structure
2. port the router to the new APIs
3. set_type_system_hir
4. run on the schema corpus
5. remove hir module
6. adding to the test suite with old hir to test the new hir
7. finish porting validation code to compiler-less mechanism
8. docs for the new architecture
9. docs for new API usage (rust inline docs + readme)
10. add performance benchmarking between new vs old vs graphql-js implementation (validation specifically)
11. example: operation manipulations
12. example: synthetic/logic based schema creation (only merge specific fields in an object type)
13. example: create a schema and use that as set_type_system_hir to start a compiler