summaryrefslogtreecommitdiff
path: root/src/Language/GraphQL/AST
AgeCommit message (Collapse)Author
2024-11-05Parse interfaces implementing interfacesEugen Wissner
2024-10-13Validate repeatable directivesEugen Wissner
2024-08-27Parse repeatable directive definitionsEugen Wissner
2024-08-06Fix GHC 9.8 warningsEugen Wissner
2024-08-04Remove unused liftA2 importEugen Wissner
2023-10-13Fix non nullable type representationEugen Wissner
…in executor error messages.
2023-02-25Encode type extensionsEugen Wissner
2023-01-26Encode schema extensionsEugen Wissner
2023-01-11Encode directive definitionsEugen Wissner
2023-01-10Encode input object typesEugen Wissner
2023-01-09Encode enumsEugen Wissner
2023-01-08Encode unionsEugen Wissner
2023-01-03Encode object type definitionsEugen Wissner
2023-01-02Encode interfaces (2018)Eugen Wissner
2022-12-27Add Semigroup and Monoid instances for DescriptionEugen Wissner
2022-12-25Encode schema definitionsEugen Wissner
2022-12-24Replace ">> pure ()" with voidv1.1.0.0Eugen Wissner
2022-10-02Add operation type encoderEugen Wissner
2022-07-01Change execute' to shouldResolveTo helper methodEugen Wissner
2022-02-16enhance query errorsDmitrii Skurikhin
2022-01-09fix empty list argument parsingDmitrii Skurikhin
2021-09-04Add CHANGELOG entries for the new executorEugen Wissner
2021-03-14Add location information to list valuesEugen Wissner
2021-02-21Fix some issues with directive definitionsBen Sinclair
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-11Document AST.Document.escapeEugen Wissner
2021-02-04Provide custom Show instances for AST valuesEugen Wissner
2021-02-03Validate valuesEugen Wissner
2020-12-17Add show instances for AST type representationEugen Wissner
2020-10-07Collect types once the schema is createdEugen Wissner
2020-10-05Validate required input fieldsEugen Wissner
2020-10-02Validate directives are in valid locationsEugen Wissner
2020-09-30Validate input object field namesEugen Wissner
2020-09-24Validate input fields have unique namesEugen Wissner
2020-09-21Validate all variables are definedEugen Wissner
2020-09-19Validate variable names are uniqueEugen Wissner
2020-09-18Validate directives are unique per locationEugen Wissner
2020-09-15Use Seq as base monad in the validatorEugen Wissner
It is more natural to implement the logic: try to apply each rule to each node.
2020-09-09Validate all fragments are usedEugen Wissner
2020-09-07Validate fragments on composite typesEugen Wissner
2020-09-05Validate fragment spread type existenceEugen Wissner
2020-08-31Validate fragment spread target existenceEugen Wissner
2020-08-26Validate anonymous operation definitionsEugen Wissner
2020-08-25Validate single root field in subscriptionsEugen Wissner
2020-08-22Remove encoder test based on old external filesEugen Wissner
2020-07-20Draft the Validation APIEugen Wissner
2020-07-11Parse subscriptionsEugen Wissner
2020-07-10Label parsers with help infoEugen Wissner
Fixes #36.
2020-07-09Parse comments in the front of definitionsEugen Wissner
2020-07-08Return parser error location in a listEugen Wissner
An error can have multiple locations which are returned in a listt with key "locations".
2020-06-30Move Core module out of ASTEugen Wissner