diff options
| author | Ben Sinclair <ben@typius.com> | 2021-02-21 02:06:27 +1100 |
|---|---|---|
| committer | Ben Sinclair <ben@typius.com> | 2021-02-21 23:35:34 +1100 |
| commit | ca0f0bd32d3334dfe7e016f11c9582c6e54e5422 (patch) | |
| tree | 3cb569418ac15c6a4af2a25c6374ac8eb00d876c /src/Language/GraphQL/Execute/Coerce.hs | |
| parent | 10e4d64052aabbbe3fd82daf83138723ae4af3b6 (diff) | |
| download | graphql-ca0f0bd32d3334dfe7e016f11c9582c6e54e5422.tar.gz | |
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.
Diffstat (limited to 'src/Language/GraphQL/Execute/Coerce.hs')
0 files changed, 0 insertions, 0 deletions