graphql/stack.yaml

resolver: lts-16.5

packages:
- .

extra-deps: []
flags: {}

pvp-bounds: both
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. 2020-07-14 19:37:56 +02:00			`resolver: lts-16.5`
Ignore graphql.cabal This file is generated and for releases another version is generated anyway. 2019-09-29 07:27:21 +02:00
Pin stack to LTS-4.2 2016-01-26 13:35:53 +01:00			`packages:`
Set STACK_ROOT to cache dependencies in the CI Set STACK_ROOT to cache dependencies between the builds. 2019-09-30 07:09:58 +02:00			`- .`
Ignore graphql.cabal This file is generated and for releases another version is generated anyway. 2019-09-29 07:27:21 +02:00
Pin stack to LTS-4.2 2016-01-26 13:35:53 +01:00			`extra-deps: []`
			`flags: {}`
Ignore graphql.cabal This file is generated and for releases another version is generated anyway. 2019-09-29 07:27:21 +02:00
			`pvp-bounds: both`