| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2021-09-04 | Add CHANGELOG entries for the new executor | Eugen Wissner | |
| 2021-09-03 | Replace the old executor | Eugen Wissner | |
| 2021-09-02 | Handle argument locations | Eugen Wissner | |
| 2021-09-01 | Adjust value completion tests | Eugen Wissner | |
| 2021-08-31 | Show the value and expected type in value completion errors | Eugen Wissner | |
| 2021-08-31 | Copy subscription code | Eugen Wissner | |
| 2021-08-31 | Handle errors | Eugen Wissner | |
| 2021-08-31 | Use sequences of selections | Eugen Wissner | |
| 2021-08-31 | Collect fields | Eugen Wissner | |
| 2021-08-31 | Skip recursive fragments and marked fields | Eugen Wissner | |
| 2021-08-31 | Inline fragment spreads | Eugen Wissner | |
| 2021-08-31 | Use directives from the Type module | Eugen Wissner | |
| 2021-08-31 | Pass variables when generating the IR | Eugen Wissner | |
| 2021-08-31 | Stub selection execution | Eugen Wissner | |
| 2021-08-31 | Rewrite the executor tree | Eugen Wissner | |
| 2021-08-31 | Provide error information for variable definitions | Eugen Wissner | |
| 2021-08-31 | Stub request execution | Eugen Wissner | |
| 2021-08-31 | Handle query errors on invalid operations | Eugen Wissner | |
| 2021-08-31 | Add new executor module | Eugen Wissner | |
| 2021-08-31 | Provide a custom Show instance for output Value | Eugen Wissner | |
| 2021-07-02 | Report subscription error locations | Eugen Wissner | |
| 2021-06-27 | Attach the field location to resolver exceptions | Eugen Wissner | |
| 2021-06-24 | Fail with a location for result coercion | Eugen Wissner | |
| The intermediate representation was further modified so that the operation definitions contain location information. Probably I should introduce a data type that generalizes fields and operations, so it contains object type, location and the selection set, so the functions don't accept so many arguments. | |||
| 2021-06-22 | Provide locations for argument errors | Eugen Wissner | |
| The executor still doesn't give an error per argument, but a single error per field with locations for all arguments. If a non-null argument isn't specified, only the error location of the field is given. If some arguments cannot be coerced, only the locations of these arguments are given, non-null arguments are ignored. This should still be improved, so the executor returns all errors at once. The transformation tree is changed, so that argument map contains locations of the arguments (but not the locations of the argument values yet). | |||
| 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-06-17 | Provide location information for interface errors | Eugen Wissner | |
| 2021-05-13 | Add constructor with additional schema types | Eugen Wissner | |
| 2021-05-12 | Add location information to the intermediate tree | Eugen Wissner | |
| 2021-05-11 | Remove unused QueryError.TransformationError | 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-09 | Provide an internal function to add errors | Eugen Wissner | |
| The old function, addErrMsg, takes only a string with an error description, but more information is required for the execution errors: locations and path. addErrMsg should be deprecated after the switching to the new addError. | |||
| 2021-05-06 | Validate non-nullable values inside lists | Eugen Wissner | |
| 2021-04-14 | Remove unused OverloadedStrings pragmas | Eugen Wissner | |
| 2021-04-12 | Traverse input object properties once | Eugen Wissner | |
| 2021-03-16 | Emit list item errors once | Eugen Wissner | |
| 2021-03-14 | Add location information to list values | 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-15 | traverseMaybe OrderedMap | Eugen Wissner | |
| 2021-02-14 | Combine value inserted into the OrderedMap | Eugen Wissner | |
| 2021-02-13 | Add OrderedMap prototype | Eugen Wissner | |
| 2021-02-11 | Document AST.Document.escape | Eugen Wissner | |
| 2021-02-04 | Provide custom Show instances for AST values | Eugen Wissner | |
| 2021-02-03 | Validate values | Eugen Wissner | |
| 2021-02-02 | Update stack snapshot to 17.x. | Eugen Wissner | |
| 2021-01-22 | Validate variable usage is allowed in objects | Eugen Wissner | |
| 2021-01-04 | Fix the type in messages when validating variables | Eugen Wissner | |
| 2020-12-27 | Rename variablesInAllowedPositionRule's variables | Eugen Wissner | |
| Name variablesInAllowedPositionRule's variables more meaningful. | |||
| 2020-12-26 | Validate variable usages are allowed in arguments | Eugen Wissner | |
| 2020-12-17 | Add show instances for AST type representation | Eugen Wissner | |
