graphql/stack.yaml, branch v0.9.0.0 GraphQL implementation in Haskell. Release 0.9.0.0 2020-07-24T19:34:31+00:00 Eugen Wissner belka@caraus.de 2020-07-24T19:34:31+00:00 adeba459a20e3fa2e74d98ae7219ef3ed41e7883 






Support subscriptions
2020-07-14T17:37:56+00:00

Eugen Wissner
belka@caraus.de

2020-07-14T17:37:56+00:00

ae2210f6598f166116abebc1163e1523d3bc627c

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.





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.







Export sum type for all GraphQL types
2020-07-06T17:10:34+00:00

Eugen Wissner
belka@caraus.de

2020-07-06T17:10:34+00:00

b2d473de8dac0f85f11a8f9985d1a9a4dfee03ab












Combine Resolver and ActionT in ResolverT
2020-06-29T11:14:23+00:00

Eugen Wissner
belka@caraus.de

2020-06-29T11:14:23+00:00

705e506c13b6c0f67ddf0195fa0d3256e7e4f9c3












Add a github actions workflow
2020-06-24T08:12:22+00:00

Eugene Wissner
belka@caraus.de

2020-06-24T07:45:25+00:00

175268b422c20ec01bb0dc3d36a53a394931b289












Fix list input coercion
2020-06-19T08:53:41+00:00

Eugen Wissner
belka@caraus.de

2020-06-19T08:53:41+00:00

91bd2d0d8155469b28749a6458e0f7a9279e3698












Skip unknown fields
2020-06-10T09:42:00+00:00

Eugen Wissner
belka@caraus.de

2020-06-10T09:42:00+00:00

c37b9c88b1f64d842ad837a18bfbe01026324abb












Add custom Eq instances to the types
2020-06-09T08:02:34+00:00

Eugen Wissner
belka@caraus.de

2020-06-09T08:02:34+00:00

fdb1268213f9ea6da33d82fc57e1b0c7874c3fe2












Resolve abstract types
2020-06-03T05:20:38+00:00

Eugen Wissner
belka@caraus.de

2020-06-03T05:20:38+00:00

93a04032886976b540f5fdb1417bd085a642f772

Objects that can be a part of an union or interface should return
__typename as string.





Objects that can be a part of an union or interface should return
__typename as string.







Define resolvers on type fields
2020-05-29T11:53:51+00:00

Eugen Wissner
belka@caraus.de

2020-05-27T21:18:35+00:00

d12577ae717512979c7654191ca65f25fc877907

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.





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.