| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-07-15 | Respect subscriptions in the executor | Eugen Wissner | |
| After the last commit there were a few places needed to be adjusted to support subscriptions. This is done and a test case is added. It is important to implement subscriptions now, because they require changes to the library API, and they are a big missing part to finish the executor. When the executor is finished, we can start to provide more stable API without breaking everything every release. Validation and introspection shouldn't require much changes to the API; AST would require some changes to report good errors after the validation - this is one thing I can think of. Fixes #5. | |||
| 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-05 | Handle errors using custom types | Eugen Wissner | |
| Fixes #32. | |||
| 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 | |
