Daniel Tschinder fde7df534d Robust type info ... There are possibilities for errors during validation if a schema is not valid when provided to TypeInfo. Most checks for validity existed, but some did not. This asks flow to make those checks required and adds the remaining ones. Important now that we allow construction of invalid schema. ref: graphql/graphql-js#1143		2018-02-15 12:22:29 +01:00
..
AST.php	Better Predicates	2018-02-13 18:04:03 +01:00
ASTDefinitionBuilder.php	Move schema validation into separate step (type constructors)	2018-02-15 12:14:08 +01:00
BlockString.php	RFC: Block String	2018-02-10 18:43:26 +01:00
BuildSchema.php	Validate schema root types and directives	2018-02-13 10:42:35 +01:00
FindBreakingChanges.php	Better Predicates	2018-02-13 18:04:03 +01:00
MixedStore.php	Global config; descriptor moved to appropriate namespace; minor cleanup	2017-07-12 13:16:34 +07:00
PairSet.php	Validation: improving overlapping fields quality	2018-02-11 17:45:35 +01:00
SchemaPrinter.php	Move schema validation into separate step (type constructors)	2018-02-15 12:14:08 +01:00
TypeComparators.php	Validate schema root types and directives	2018-02-13 10:42:35 +01:00
TypeInfo.php	Robust type info	2018-02-15 12:22:29 +01:00
Utils.php	Move schema validation into separate step (type constructors)	2018-02-15 12:14:08 +01:00
Value.php	Preserve original coercion errors, improve error quality.	2018-02-13 16:51:44 +01:00