graphql/src/Language/GraphQL/AST
Ben Sinclair ca0f0bd32d Fix some issues with directive definitions
I found some issues with directive definitions:

- I couldn't use `on FIELD_DEFINITION`, I believe because `FIELD` was parsed
  first in `executableDirectiveLocation`. I've combined both
  `executableDirectiveLocation` and `typetypeSystemDirectiveLocation` into one
  function which can reorder them to ensure every directive location gets a fair
  chance at parsing.

Not actually to do with directives, some literals weren't being parsed
correctly.

- The GraphQL spec defines list to be `[]` or `[Value]`, but empty literal lists
  weren't being parsed correctly because of using `some` instead of `many`.

- The GraphQL spec defines objects to be `{}` or `{Name: Value}`, but empty
  literal objects had the same issue.
2021-02-21 23:35:34 +11:00
..
DirectiveLocation.hs Validate directives are in valid locations 2020-10-02 06:31:38 +02:00
Document.hs Document AST.Document.escape 2021-02-11 12:02:08 +01:00
Encoder.hs Provide custom Show instances for AST values 2021-02-04 08:12:12 +01:00
Lexer.hs Validate directives are unique per location 2020-09-18 07:32:58 +02:00
Parser.hs Fix some issues with directive definitions 2021-02-21 23:35:34 +11:00