graphql/src/Language/GraphQL/AST, branch v1.1.0.0 GraphQL implementation in Haskell. Replace ">> pure ()" with void 2022-12-24T17:59:40+00:00 Eugen Wissner belka@caraus.de 2022-12-24T17:59:40+00:00 a5cf0a32e82dbf6e093ebca47917a84276332b63 






Add operation type encoder
2022-10-02T09:38:53+00:00

Eugen Wissner
belka@caraus.de

2022-10-02T09:38:53+00:00

bf2e4925b45991476c430bd635d8fbabe7cbecbf












Change execute' to shouldResolveTo helper method
2022-07-01T10:18:02+00:00

Eugen Wissner
belka@caraus.de

2022-07-01T10:18:02+00:00

2f19093803f8d852e1488dc112ae4aa9d0fcb212












enhance query errors
2022-02-16T07:58:16+00:00

Dmitrii Skurikhin
dmitrii.sk@gmail.com

2022-02-11T19:50:53+00:00

8503c0f288201223776f9962438c577241f08c9d












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












Add CHANGELOG entries for the new executor
2021-09-04T05:12:34+00:00

Eugen Wissner
belka@caraus.de

2021-09-04T05:12:34+00:00

de4f69ab0312edfd7c0deb033aa6103442eb3ec8












Add location information to list values
2021-03-14T11:19:30+00:00

Eugen Wissner
belka@caraus.de

2021-03-14T11:19:30+00:00

4d762d635666a954000be76832303eb3170f4ee2












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.







Document AST.Document.escape
2021-02-11T11:02:08+00:00

Eugen Wissner
belka@caraus.de

2021-02-11T11:02:08+00:00

1e8405a6d6de8d7a5a1323ba11e48fb4fb852b80












Provide custom Show instances for AST values
2021-02-04T07:12:12+00:00

Eugen Wissner
belka@caraus.de

2021-02-04T07:12:12+00:00

b27da54bf4d4c75447c1cad4329c2b28ae2c6c82