summaryrefslogtreecommitdiff
path: root/Data/GraphQL/Schema.hs
AgeCommit message (Collapse)Author
2016-02-17GardenDanny Navarro
2016-02-15Initial support for variable substitutionDanny Navarro
The correspondent end-to-end test has been ported. The variable definition still needs to be checked.
2016-02-12Handle Field arguments in Schema definitionDanny Navarro
The `Schema` has been overhauled to make `Output` monomorphic. Traversing the `GraphQL` document is handled implicitly while defining the `Schema`. The 4th end-to-end test from `graphql-js` has been ported.
2016-02-09Handle Output enumerations in Schema definitionDanny Navarro
The third end-to-end test from graphql-js was implemented.
2016-01-30Generalize `Maybe` type constructor to any MonadDanny Navarro
This allows schema definitions with side-effects for any type with a Monadic/Alternative implementation like IO for example.
2016-01-26GardenDanny Navarro
2016-01-26Rough implementation of `execute`Danny Navarro
The first end-to-end test taken from `graphql-js` passes but this still needs to be extended to support more general cases. - `Data.GraphQL.Schema` has been heavily modified to support the execution model. More drastic changes are expected in this module. - When defining a `Schema` ordinary functions taking fields as input are being used instead of maps. This makes the implementation of `execute` easier, and, arguably, makes `Schema` definitions more *Haskellish*. - Drop explicit `unordered-containers` dependency. `Aeson.Value`s and field functions should be good enough for now.
2015-10-19Implement first StarWars end-to-end testDanny Navarro
`execute` still needs to be implemented.
2015-10-17Test fixtures for Schema toplevelDanny Navarro
This includes simplications to the Schema data types.
2015-10-17Initial stub for a `GraphQL` and `execute`Danny Navarro