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-07-06	Export sum type for all GraphQL types	Eugen Wissner

2020-07-02	Merge Trans and Type.Out modules	Eugen Wissner

2020-06-30	Move Core module out of AST	Eugen Wissner

2020-06-29	Combine Resolver and ActionT in ResolverT	Eugen Wissner

2020-06-13	Coerce result	Eugen Wissner
	Fixes #45.
2020-06-12	Merge selection sets	Eugen Wissner

2020-06-10	Skip unknown fields	Eugen Wissner

2020-06-09	Add custom Eq instances to the types	Eugen Wissner

2020-06-07	Add description to the enum type values	Eugen Wissner

2020-06-06	Coerce argument values properly	Eugen Wissner
	Fixes #44.
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.