Validation Tracking

[jlouis]

Background

We need to have a place where we track validations. We begin this work by building the complete list, then mark what we already have covered. Things not covered are pulled into their own issues for further tracking.

Checklist

From the Oct2016 specification:

• 5.1.1 Named Operation Definitions
• 5.1.1.1 Operation Name Uniqueness
• 5.1.2 Anonymous Operation Definitions
• 5.1.2.1 Lone Anonymous Operation
• 5.2.1 Field Selections on Objects, Interfaces, and Unions Types
• 5.2.2 Field Selection Merging
• 5.2.3 Leaf Field Selections
• 5.3.1 Argument Names
• 5.3.2 Argument Uniqueness
• 5.3.3 Argument Values Type Correctness
• 5.3.3.1 Compatible Values
• 5.3.3.2 Required Non-Null Arguments
• 5.4.1 Fragment Declarations
• 5.4.1.1 Fragment Name Uniqueness
• 5.4.1.2 Fragment Spread Type Existence
• 5.4.1.3 Fragments On Composite Types
• 5.4.1.4 Fragments Must Be Used
• 5.4.2 Fragment Spreads
• 5.4.2.1 Fragment spread target defined
• 5.4.2.2 Fragment spreads must not form cycles
• 5.4.2.3 Fragment spread is possible
• 5.4.2.3.1 Object Spreads In Object Scope
• 5.4.2.3.2 Abstract Spreads in Object Scope
• 5.4.2.3.3 Object Spreads In Abstract Scope
• 5.4.2.3.4 Abstract Spreads in Abstract Scope
• 5.5.1 Input Object Field Uniqueness
• 5.6.1 Directives Are Defined
• 5.6.2 Directives Are In Valid Locations
• 5.6.3 Directives Are Unique Per Location
• 5.7.1 Variable Uniqueness
• 5.7.2 Variable Default Values Are Correctly Typed
• 5.7.3 Variables Are Input Types
• 5.7.4 All Variable Uses Defined
• 5.7.5 All Variables Used
• 5.7.6 All Variable Usages are Allowed

[jlouis]

PR #71 tracks 5.7.4, PR #70 tracks 5.7.6

[jlouis]

The checked validations are already handled by the code base with a test.

[jlouis]

PR #108 tracks 5.2.2

[jlouis]

5.3.3.1 is handled already by the type checker.

[jlouis]

5.3.3.2 is also handled by the type checker.

[jlouis]

PR #109 tracks 5.4.1.4

[jlouis]

A large number of issues were closed just now, so update the checklist with those.