summaryrefslogtreecommitdiff
path: root/tests/Language/GraphQL/ExecuteSpec.hs
AgeCommit message (Collapse)Author
2024-10-14Replace gql in Encoder tests with multiline stringEugen Wissner
2023-11-08Add a test for the input object coercion issueEugen Wissner
2023-10-13Fix non nullable type representationEugen Wissner
…in executor error messages.
2023-02-24Fix resolvers returning a list in the reverse orderEugen Wissner
2022-12-24Fix GHC 9.2 warnings and deprecationsEugen Wissner
- Fix GHC 9.2 warnings - Convert comments to proper deprecations
2022-07-02Eliminate non-exhaustive patterns in ExecuteSpecEugen Wissner
2022-07-01Change execute' to shouldResolveTo helper methodEugen Wissner
2022-02-16enhance query errorsDmitrii Skurikhin
2022-01-07fix index position in error pathDmitrii Skurikhin
2021-12-24Put JSON support behind a flagEugen Wissner
2021-09-22Don't append a trailing newline in gqlEugen Wissner
2021-09-17Test nullability on value completionEugen Wissner
2021-09-03Replace the old executorEugen Wissner
2021-09-02Handle argument locationsEugen Wissner
2021-09-01Adjust value completion testsEugen Wissner
2021-06-27Attach the field location to resolver exceptionsEugen Wissner
2021-06-24Fail with a location for result coercionEugen 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-22Provide locations for argument errorsEugen 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-18Fix merging fields with argumentsEugen 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-17Provide location information for interface errorsEugen Wissner
2021-05-13Add constructor with additional schema typesEugen Wissner
2021-05-12Add location information to the intermediate treeEugen Wissner
2021-05-09Provide an internal function to add errorsEugen 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.
2020-10-07Collect types once the schema is createdEugen Wissner
2020-09-28Validate arguments are definedEugen Wissner
2020-09-11Validate fragments don't form cyclesEugen Wissner
2020-07-17Constrain base monad to MonadCatchEugen Wissner
Let's try MonadThrow/MonadCatch. It looks nice at a first glance. The monad transformer stack contains only the ReaderT, less lifts are required. Exception subtyping is easier, the user can (and should) define custom error types and throw them. And it is still possible to use pure error handling, if someone doesn't like runtime exceptions or need to run a query in a pure environment. Fixes #42.
2020-07-15Respect subscriptions in the executorEugen Wissner
After the last commit there were a few places needed to be adjusted to support subscriptions. This is done and a test case is added. It is important to implement subscriptions now, because they require changes to the library API, and they are a big missing part to finish the executor. When the executor is finished, we can start to provide more stable API without breaking everything every release. Validation and introspection shouldn't require much changes to the API; AST would require some changes to report good errors after the validation - this is one thing I can think of. Fixes #5.
2020-07-14Support subscriptionsEugen Wissner
This is experimental support. The implementation is based on conduit and is boring. There is a new resolver data constructor that should create a source event stream. The executor receives the events, pipes them through the normal execution and puts them into the response stream which is returned to the user. - Tests are missing. - The executor should check field value resolver on subscription types. - The graphql function should probably return (Either ResponseEventStream Response), but I'm not sure about this. It will make the usage more complicated if no subscriptions are involved, but with the current API implementing subscriptions is more difficult than it should be.
2020-07-05Handle errors using custom typesEugen Wissner
Fixes #32.
2020-06-29Combine Resolver and ActionT in ResolverTEugen Wissner
2020-06-13Coerce resultEugen Wissner
Fixes #45.
2020-06-12Merge selection setsEugen Wissner
2020-06-10Skip unknown fieldsEugen Wissner
generated by cgit v1.2.3 (git 2.26.2) at 2026-06-26 22:13:41 +0000