| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2021-02-14 | Combine value inserted into the OrderedMap | Eugen Wissner | |
| 2021-02-13 | Add OrderedMap prototype | Eugen Wissner | |
| 2020-10-07 | Collect types once the schema is created | Eugen Wissner | |
| 2020-10-05 | Validate required input fields | Eugen Wissner | |
| 2020-09-30 | Validate input object field names | Eugen Wissner | |
| 2020-09-28 | Validate arguments are defined | Eugen Wissner | |
| 2020-09-26 | Validate field selections on composite types | Eugen Wissner | |
| 2020-09-24 | Validate input fields have unique names | Eugen Wissner | |
| 2020-09-21 | Validate all variables are defined | Eugen Wissner | |
| 2020-09-20 | Validate fragments are input types | Eugen Wissner | |
| 2020-09-19 | Validate variable names are unique | Eugen Wissner | |
| 2020-09-18 | Validate directives are unique per location | Eugen Wissner | |
| 2020-09-16 | Move path to the execution error | Eugen Wissner | |
| Since it isn't possible to get a path during validation, without executing the query. | |||
| 2020-09-15 | Use Seq as base monad in the validator | Eugen Wissner | |
| It is more natural to implement the logic: try to apply each rule to each node. | |||
| 2020-09-09 | Validate all fragments are used | Eugen Wissner | |
| 2020-09-07 | Validate fragments on composite types | Eugen Wissner | |
| 2020-09-05 | Validate fragment spread type existence | Eugen Wissner | |
| 2020-08-31 | Validate fragment spread target existence | Eugen Wissner | |
| 2020-08-25 | Validate single root field in subscriptions | Eugen Wissner | |
| 2020-08-22 | Remove encoder test based on old external files | Eugen Wissner | |
| 2020-07-20 | Draft the Validation API | Eugen Wissner | |
| 2020-07-17 | Constrain base monad to MonadCatch | Eugen Wissner | |
| Let's try MonadThrow/MonadCatch. It looks nice at a first glance. The monad transformer stack contains only the ReaderT, less lifts are required. Exception subtyping is easier, the user can (and should) define custom error types and throw them. And it is still possible to use pure error handling, if someone doesn't like runtime exceptions or need to run a query in a pure environment. Fixes #42. | |||
| 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-11 | Parse subscriptions | Eugen Wissner | |
| 2020-07-06 | Export sum type for all GraphQL types | Eugen Wissner | |
| 2020-07-02 | Merge Trans and Type.Out modules | Eugen Wissner | |
| 2020-06-30 | Move Core module out of AST | Eugen Wissner | |
| 2020-06-29 | Combine Resolver and ActionT in ResolverT | Eugen Wissner | |
| 2020-06-19 | Fix list input coercion | 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 | |
| 2020-06-09 | Add custom Eq instances to the types | Eugen Wissner | |
| 2020-06-07 | Add description to the enum type values | Eugen Wissner | |
| 2020-06-06 | Coerce argument values properly | Eugen Wissner | |
| Fixes #44. | |||
| 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-22 | Reject variables as default values | Eugen Wissner | |
| 2020-05-21 | Coerce variable values | Eugen Wissner | |
| 2020-01-01 | Rewrite argument list to argument map | Eugen Wissner | |
| 2019-12-30 | Replace substitution function with a map | Eugen Wissner | |
| It makes using variables with queries more approachable, but some work still has to be done. - The type `Subs` should be renamed and moved out of `Schema`, together with `AST.Core.Value` probably. - Some kind of conversion should be possible from a user-defined input type T to the Value. So the final HashMap should have a type like `HashMap name a`, where a is an instance of a potential typeclass InputType. | |||
| 2019-12-28 | Move AST to AST.Document | Eugen Wissner | |
| 2019-12-26 | Add definition module | Eugen Wissner | |
| 2019-12-25 | Replace AST.Selection data constructors | Eugen Wissner | |
| 2019-12-18 | Move Execute.Directive to Type.Directive | Eugen Wissner | |
| Just to roughly follow the structure of the reference implementation. | |||
