| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2021-09-23 | Remove raw-strings-qq | Eugen Wissner | |
| 2020-10-07 | Collect types once the schema is created | Eugen Wissner | |
| 2020-09-28 | Validate arguments are defined | Eugen Wissner | |
| 2020-09-26 | Validate field selections on composite types | Eugen Wissner | |
| 2020-09-11 | Validate fragments don't form cycles | Eugen Wissner | |
| 2020-09-04 | Collect types from the subscription root | Eugen Wissner | |
| 2020-07-19 | Return a stream as well from graphql* functions | Eugen Wissner | |
| 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-06-29 | Combine Resolver and ActionT in ResolverT | Eugen Wissner | |
| 2020-06-19 | Fix list input coercion | Eugen Wissner | |
| 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. | |||
| 2020-05-26 | Add Union and Interface type definitions | Eugen Wissner | |
| 2020-05-25 | Split input/output types and values into 2 modules | Eugen Wissner | |
| 2020-05-24 | Check point | Eugen Wissner | |
| 2020-05-23 | Don't fail on invalid fragments and variables | Eugen Wissner | |
| 2020-05-21 | Coerce variable values | Eugen Wissner | |
| 2020-05-14 | Add basic output object type support | Eugen Wissner | |
| 2020-05-13 | Accept resolvers given by the user as is | Eugen Wissner | |
| 2020-05-10 | Separate Query and Mutation resolvers | Eugen Wissner | |
| Fixes #33 . | |||
| 2019-12-02 | Consider __typename when evaluating fragments | Eugen Wissner | |
| Fixes #30. | |||
| 2019-11-14 | Fail on cyclic fragments, fix #22 | Eugen Wissner | |
| 2019-11-12 | Support nested fragments in any order | Eugen Wissner | |
| Fix #19. | |||
| 2019-11-09 | Support nested fragments | Eugen Wissner | |
| ... without forward lookup. | |||
| 2019-10-19 | Handle top-level fragments | Eugen Wissner | |
| Fixes #17. | |||
| 2019-10-11 | Inline fragments without type | Eugen Wissner | |
| Fixes #11. | |||
| 2019-10-08 | Support inline fragments on types | Eugen Wissner | |
| 2019-09-13 | Add pending inline fragment tests | Eugen Wissner | |
