Garden

Data/GraphQL/AST.hs

@@ -61,8 +61,8 @@ type TypeCondition = NamedType
 -- * Values
 
 data Value = ValueVariable Variable
-           | ValueInt Int -- TODO: Should this be `Integer`?
+           | ValueInt Int
-           | ValueFloat Double -- TODO: Should this be `Scientific`?
+           | ValueFloat Double
            | ValueBoolean Bool
            | ValueString Text
            | ValueEnum Name

Data/GraphQL/Parser.hs

@@ -148,8 +148,9 @@ typeCondition = namedType
 -- explicit types use the `typedValue` parser.
 value :: Parser Value
 value = ValueVariable <$> variable
-        -- TODO: Handle arbitrary precision.
+    -- TODO: Handle maxBound, Int32 in spec.
     <|> ValueInt      <$> tok (signed decimal)
+    -- There is a stock `parser` for double but not for float.
     <|> ValueFloat    <$> tok (signed double)
     <|> ValueBoolean  <$> bool
     -- TODO: Handle escape characters, unicode, etc

README.md

@@ -21,6 +21,6 @@ See the TODO file for more concrete tasks.
 
 Suggestions, contributions and bug reports are welcome.
 
-Feel free to contact me, jdnavarro, on the #haskell channel on the
+Feel free to contact on Slack in [#haskell on
-[GraphQL Slack Server](https://graphql.slack.com). You can obtain an
+GraphQL](https://graphql.slack.com/messages/haskell/). You can obtain an
 invitation [here](https://graphql-slack.herokuapp.com/).

TODO

@@ -1,21 +1,23 @@
 ## AST
 - Simplify unnecessary `newtypes` with type synonyms
+- Simplify wrapper type constructors. Some types can be just constructors.
 - Data type accessors
-- Deal with Strictness/unboxing
+- Deal with strictness/unboxing
-- Deal with Location
+- Deal with location
 
 ## Parser
 - Secure Names
 - Optimize `name` and `whiteSpace`: `take...`, `T.fold`, ...
 - Handle escape characters in string literals
 - Guard for `on` in `FragmentSpread`
-- Tests!
 - Handle `[Const]` grammar parameter. Need examples
-- Arbitrary precision for number values?
+- Handle `maxBound` Int values.
-- Handle errors. Perhaps port to `parsers` or use a lexer and
+- Diagnostics. Perhaps port to `parsers` and use `trifecta` for diagnostics,
- `regex-applicative`
+  and `attoparsec` for performance.
+- Improve comment handling: perhaps front the main parser with a lexer.
 
 ## Tests
 
-- Golden data within package, `path_graphql` macro.
+- Pretty print golden result
-- Pretty Print golden result
+
+## Docs!

graphql.cabal

@@ -34,6 +34,7 @@ test-suite golden
   hs-source-dirs:      tests
   main-is:             golden.hs
   ghc-options:         -Wall
+  other-modules:       Paths_graphql
   build-depends:       base >= 4.6 && <5,
                        bytestring,
                        text,