Eugen Wissner
44dc80bb37
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. |
||
|---|---|---|
| docs/tutorial | ||
| src/Language | ||
| tests | ||
| .gitignore | ||
| CHANGELOG.md | ||
| LICENSE | ||
| package.yaml | ||
| README.md | ||
| semaphoreci.sh | ||
| Setup.hs | ||
| stack.yaml | ||
Haskell GraphQL
GraphQL implementation in Haskell.
This implementation is relatively low-level by design, it doesn't provide any mappings between the GraphQL types and Haskell's type system and avoids compile-time magic. It focuses on flexibility instead, so other solutions can be built on top of it.
State of the work
For now this only provides a parser and a printer for the GraphQL query
language and allows to execute queries and mutations without the schema
validation step. But the idea is to be a Haskell port of
graphql-js.
For the list of currently missing features see issues marked as "not implemented".
Documentation
API documentation is available through hackage.
You'll also find a small tutorial with some examples under docs/tutorial.
Contact
Suggestions, contributions and bug reports are welcome.
Should you have questions on usage, please open an issue and ask – this helps to write useful documentation.
Feel free to contact on Slack in #haskell on GraphQL. You can obtain an invitation here.