Go to file

Tom Hunger 87c92e9d6e Parse number as scientific and interpret meaning separately.

The current parser will fail parsing floats because it parses an int,
and then stumbles on the dot.

To fix I interpret the value with the scientific library which already
is a dependency through attoparsec, so we're not introducing any extra
downloads or compiling.

I think this is still subtly wrong because "10.0" will be parsed as
ValueInt, but because input argument ints are allowed to be coerced
into doubles (according to the spec) this is probably acceptable.

2016-12-09 00:03:20 +00:00

Data

Parse number as scientific and interpret meaning separately.

2016-12-09 00:03:20 +00:00

docs/tutorial

Merge branch 'all-improvements'

2016-03-15 14:02:34 +01:00

tests

add tests for errors in queries for queries in starwars tests

2016-07-08 18:10:14 -04:00

.ghci

Convenient imports for ghci

2015-09-14 17:02:43 +02:00

.gitignore

Garden

2016-01-26 13:38:02 +01:00

.travis.yml

Add travis support

2015-09-16 10:51:53 +02:00

AUTHORS.md

add pweaver to contributors

2016-07-09 10:55:16 -04:00

CHANGELOG.md

Version Bump

2015-09-22 14:27:10 +02:00

graphql.cabal

Parse number as scientific and interpret meaning separately.

2016-12-09 00:03:20 +00:00

LICENSE

Initial commit

2015-09-12 12:54:05 +02:00

README.md

Version Bump

2015-09-22 14:27:10 +02:00

Setup.hs

Initial commit

2015-09-12 12:54:05 +02:00

stack.yaml

Garden

2016-02-17 13:20:56 +01:00

TODO

Version Bump

2015-09-22 14:27:10 +02:00

README.md

Haskell GraphQL

For now this only provides the data types to represent the GraphQL AST, but the idea is to be a Haskell port of graphql-js. Next releases should include:

GraphQL AST
Parser for the GraphQL language. See TODO for limitations.
Printer for GraphQL. This is not pretty yet.
GraphQL Schema AST.
Parser for the GraphQL Schema language.
Printer for the GraphQL Schema language.
Interpreter of GraphQL requests.
Utilities to define GraphQL types and schema.

See the TODO file for more concrete tasks.

Contact

Suggestions, contributions and bug reports are welcome.

Feel free to contact on Slack in #haskell on GraphQL. You can obtain an invitation here.