graphql - GraphQL implementation in Haskell.

Age	Commit message (Collapse)	Author
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.
2020-06-29	Combine Resolver and ActionT in ResolverT	Eugen Wissner

2020-06-19	Fix list input coercion	Eugen Wissner

2020-06-03	Resolve abstract types	Eugen Wissner
	Objects that can be a part of an union or interface should return __typename as string.
2020-05-29	Define resolvers on type fields	Eugen Wissner
	Returning resolvers from other resolvers isn't supported anymore. Since we have a type system now, we define the resolvers in the object type fields and pass an object with the previous result to them.
2020-05-26	Add Union and Interface type definitions	Eugen Wissner

2020-05-25	Split input/output types and values into 2 modules	Eugen Wissner

2020-05-24	Check point	Eugen Wissner

2020-05-23	Don't fail on invalid fragments and variables	Eugen Wissner

2020-05-21	Coerce variable values	Eugen Wissner

2020-05-14	Add basic output object type support	Eugen Wissner

2020-05-13	Accept resolvers given by the user as is	Eugen Wissner

2020-05-10	Separate Query and Mutation resolvers	Eugen Wissner
	Fixes #33 .
2019-12-06	Support directives (skip and include)	Eugen Wissner
	Fixes #24.