graphql - GraphQL implementation in Haskell.

Age	Commit message (Collapse)	Author
2021-07-02	Report subscription error locations	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-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-02-19	Replace Map with OrderedMap	Eugen Wissner

2020-07-17	Constrain base monad to MonadCatch	Eugen 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-14	Support subscriptions	Eugen 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.