graphql/tests/Language/GraphQL/AST/ParserSpec.hs, branch v1.1.0.0 GraphQL implementation in Haskell. add Arbitrary instances for AST.Document, add random arguments Parser test 2022-02-14T18:18:13+00:00 Dmitrii Skurikhin dmitrii.sk@gmail.com 2022-02-02T17:52:46+00:00 05e6aa4c95782e6525f37edb323959da4d65898e 






fix empty list argument parsing
2022-01-09T08:00:56+00:00

Dmitrii Skurikhin
dmitrii.sk@gmail.com

2022-01-06T13:49:54+00:00

0c8edae90af9ca9033dc106756cf8ce29c08087b












Remove raw-strings-qq
2021-09-23T06:23:38+00:00

Eugen Wissner
belka@caraus.de

2021-09-23T06:23:38+00:00

fbfbb3e73f4adc973fd2b515c4fb665e1556a214












Fix some issues with directive definitions
2021-02-21T12:35:34+00:00

Ben Sinclair
ben@typius.com

2021-02-20T15:06:27+00:00

ca0f0bd32d3334dfe7e016f11c9582c6e54e5422

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.





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.







Validate directives are unique per location
2020-09-18T05:32:58+00:00

Eugen Wissner
belka@caraus.de

2020-09-18T05:32:58+00:00

9a08aa5de73e225a9a76017aee4886ce7f6eccec












Draft the Validation API
2020-07-20T19:29:12+00:00

Eugen Wissner
belka@caraus.de

2020-07-20T19:29:12+00:00

44d506d4b57e450480cf9c476bd927a43ad9c25d












Parse subscriptions
2020-07-11T04:34:10+00:00

Eugen Wissner
belka@caraus.de

2020-07-11T04:34:10+00:00

840e129c4496b4e8145480d2b3c3cb34f505702e












Parse comments in the front of definitions
2020-07-09T06:11:12+00:00

Eugen Wissner
belka@caraus.de

2020-07-09T06:11:12+00:00

28781586a5ecf31630730ef0d8dbdbfe6041e7d3












Reject variables as default values
2020-05-22T08:11:48+00:00

Eugen Wissner
belka@caraus.de

2020-05-22T08:11:48+00:00

26cc53ce0678d48bf7d5550df65171e6bf5288d2












Try all extension parsers
2020-01-28T10:08:28+00:00

Eugen Wissner
belka@caraus.de

2020-01-28T10:08:28+00:00

e8b82122c646ba159146c986cc8983d66f790142