| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2023-11-08 | Add a test for the input object coercion issue | Eugen Wissner | |
| 2023-10-14 | Add a CHANGELOG entry for the show type fix | Eugen Wissner | |
| 2023-08-03 | Remove leading carriage return in gql | Eugen Wissner | |
| 2023-04-25 | Support hspec 2.11v1.2.0.1 | Eugen Wissner | |
| 2023-03-23 | Update web links | Eugen Wissner | |
| 2023-02-28 | Release 1.2.0.0v1.2.0.0 | Eugen Wissner | |
| 2023-02-26 | Remove JSON support in the core package | Eugen Wissner | |
| 2023-02-25 | Encode type extensions | Eugen Wissner | |
| 2023-02-24 | Fix resolvers returning a list in the reverse order | Eugen Wissner | |
| 2022-12-27 | Add Semigroup and Monoid instances for Description | Eugen Wissner | |
| 2022-12-25 | Encode schema definitions | Eugen Wissner | |
| 2022-12-24 | Fix GHC 9.2 warnings and deprecations | Eugen Wissner | |
| - Fix GHC 9.2 warnings - Convert comments to proper deprecations | |||
| 2022-10-02 | Add operation type encoder | Eugen Wissner | |
| 2022-06-30 | Document usage of the json flag | Eugen Wissner | |
| 2022-03-31 | Remove deprecated Error functions | Eugen Wissner | |
| 2022-03-27 | Allow version 2.0 of the text package.v1.0.3.0 | Eugen Wissner | |
| 2022-02-16 | enhance query errors | Dmitrii Skurikhin | |
| 2022-02-14 | add Arbitrary instances for AST.Document, add random arguments Parser test | Dmitrii Skurikhin | |
| 2022-01-09 | fix empty list argument parsing | Dmitrii Skurikhin | |
| 2022-01-07 | Add unreleased changelog entry | Eugen Wissner | |
| 2022-01-07 | fix index position in error path | Dmitrii Skurikhin | |
| 2021-12-26 | Release 1.0.2.0v1.0.2.0 | Eugen Wissner | |
| 2021-12-24 | Put JSON support behind a flag | Eugen Wissner | |
| 2021-12-22 | Add Serialize and VariableValue value instances | Eugen Wissner | |
| - `Serialize` instance for `Type.Definition.Value`. - `VariableValue` instance for `Type.Definition.Value`. It makes it possible to use the library without an additional serialization format like JSON. | |||
| 2021-09-27 | Release 1.0.1.0v1.0.1.0 | Eugen Wissner | |
| 2021-09-21 | Add TH module with gql quasi quoter | Eugen Wissner | |
| 2021-09-05 | Deprecate unused functions from the old executor | Eugen Wissner | |
| 2021-09-04 | Add CHANGELOG entries for the new executor | Eugen Wissner | |
| 2021-08-31 | Provide a custom Show instance for output Value | Eugen Wissner | |
| 2021-07-04 | Release 1.0.0.0v1.0.0.0 | Eugen Wissner | |
| 2021-07-02 | Report subscription error locations | Eugen Wissner | |
| 2021-06-18 | Fix merging fields with arguments | Eugen Wissner | |
| executeField shouldn't assume that a selection has only one field with a given name, but it should take the first field. The underlying cause is a wrong pattern, which (because of the laziness) is executed only if the field has arguments. | |||
| 2021-05-13 | Add constructor with additional schema types | Eugen Wissner | |
| 2021-05-10 | Deprecate internal error generation functions | Eugen Wissner | |
| The functions generating errors in the executor should be changed anyway when we provide better error messages from the executor, with the error location and response path. So public definitions of these functions are deprecated now and they are replaced by more generic functions in the executor code. | |||
| 2021-05-06 | Validate non-nullable values inside lists | Eugen Wissner | |
| 2021-04-12 | Traverse input object properties once | Eugen Wissner | |
| 2021-03-16 | Emit list item errors once | Eugen Wissner | |
| 2021-02-21 | Fix some issues with directive definitions | Ben 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-19 | Replace Map with OrderedMap | Eugen Wissner | |
| 2021-02-11 | Document AST.Document.escape | Eugen Wissner | |
| 2021-02-07 | Release 0.11.1.0v0.11.1.0 | Eugen Wissner | |
| 2021-02-06 | Split validation rule tests in contexts | Eugen Wissner | |
| 2021-02-04 | Provide custom Show instances for AST values | Eugen Wissner | |
| 2021-02-03 | Validate values | Eugen Wissner | |
| 2020-12-26 | Validate variable usages are allowed in arguments | Eugen Wissner | |
| 2020-12-17 | Add show instances for AST type representation | Eugen Wissner | |
| 2020-12-14 | Implement Show class for GraphQL type definitions | Eugen Wissner | |
| .. in the `Type` modules. | |||
| 2020-11-19 | Validate fragment spreads are possible | Eugen Wissner | |
| 2020-11-17 | Collect interface implementations | Eugen Wissner | |
| 2020-11-15 | Implement basic "Field Selection Merging" rule | Eugen Wissner | |
 |
index : graphql | |
| GraphQL implementation in Haskell. |
| summaryrefslogtreecommitdiff |
path: root/CHANGELOG.md