summaryrefslogtreecommitdiff
path: root/stack.yaml
diff options
context:
space:
mode:
authorEugen Wissner <belka@caraus.de>2020-07-14 19:37:56 +0200
committerEugen Wissner <belka@caraus.de>2020-07-14 19:37:56 +0200
commitae2210f6598f166116abebc1163e1523d3bc627c (patch)
tree02b18f29d0b025a702366e70405dbcc203092c96 /stack.yaml
parent840e129c4496b4e8145480d2b3c3cb34f505702e (diff)
downloadgraphql-ae2210f6598f166116abebc1163e1523d3bc627c.tar.gz
Support subscriptions
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.
Diffstat (limited to 'stack.yaml')
-rw-r--r--stack.yaml2
1 files changed, 1 insertions, 1 deletions
diff --git a/stack.yaml b/stack.yaml
index 65e78cc..513705a 100644
--- a/stack.yaml
+++ b/stack.yaml
@@ -1,4 +1,4 @@
-resolver: lts-16.4
+resolver: lts-16.5
packages:
- .