From 933cfd2852d4f4321c03564a9cc351e3508ba73c Mon Sep 17 00:00:00 2001
From: Danny Navarro <j@dannynavarro.net>
Date: Sun, 18 Dec 2016 12:19:59 -0300
Subject: Tokenize number parser

The essential change hidden behind the code golfing is using the `tok`
combinator. This was making fail the Kitchen Sink test.
---
 tests/tasty.hs | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

(limited to 'tests')

diff --git a/tests/tasty.hs b/tests/tasty.hs
index 791bfbb..fa9bedf 100644
--- a/tests/tasty.hs
+++ b/tests/tasty.hs
@@ -22,7 +22,7 @@ main = defaultMain . testGroup "Tests" . (: [SW.test]) =<< ksTest
 
 ksTest :: IO TestTree
 ksTest = testCase "Kitchen Sink"
-                   <$> (assertEqual "Encode" <$> expected <*> actual)
+     <$> (assertEqual "Encode" <$> expected <*> actual)
   where
     expected = Text.readFile
            =<< getDataFileName "tests/data/kitchen-sink.min.graphql"
@@ -30,4 +30,3 @@ ksTest = testCase "Kitchen Sink"
     actual = either (error "Parsing error!") Encoder.document
           .  parseOnly Parser.document
          <$> expected
-
-- 
cgit v1.2.3