graphql/tests/Test, branch v0.6.0.0 GraphQL implementation in Haskell. Fail on cyclic fragments, fix #22 2019-11-14T19:40:09+00:00 Eugen Wissner belka@caraus.de 2019-11-13T19:40:09+00:00 115aa026724a688bc7ca57d622c83d0ccb2d2bb2 






Support nested fragments in any order
2019-11-12T09:47:10+00:00

Eugen Wissner
belka@caraus.de

2019-11-11T14:46:52+00:00

31c516927d75a5431c171f4d5dbd3bf0cd32956e

Fix #19.





Fix #19.







Support nested fragments
2019-11-09T22:24:31+00:00

Eugen Wissner
belka@caraus.de

2019-11-09T22:24:31+00:00

1dd6b7b013dfe2092859ddc3850944a9925a45dd

... without forward lookup.





... without forward lookup.







Move related modules to Language.GraphQL.AST
2019-11-03T10:00:18+00:00

Eugen Wissner
belka@caraus.de

2019-11-03T09:42:10+00:00

73fc334bf8d7bd6d8b83143995844ca0968ceeda

Fixes #18.

- `Language.GraphQL.Encoder` moved to `Language.GraphQL.AST.Encoder`.
- `Language.GraphQL.Parser` moved to `Language.GraphQL.AST.Parser`.
- `Language.GraphQL.Lexer` moved to `Language.GraphQL.AST.Lexer`.
- All `Language.GraphQL.AST.Value` data constructor prefixes were removed. The
  module should be imported qualified.
- All `Language.GraphQL.AST.Core.Value` data constructor prefixes were removed.
  The module should be imported qualified.
- `Language.GraphQL.AST.Transform` is now isn't exposed publically anymore.





Fixes #18.

- `Language.GraphQL.Encoder` moved to `Language.GraphQL.AST.Encoder`.
- `Language.GraphQL.Parser` moved to `Language.GraphQL.AST.Parser`.
- `Language.GraphQL.Lexer` moved to `Language.GraphQL.AST.Lexer`.
- All `Language.GraphQL.AST.Value` data constructor prefixes were removed. The
  module should be imported qualified.
- All `Language.GraphQL.AST.Core.Value` data constructor prefixes were removed.
  The module should be imported qualified.
- `Language.GraphQL.AST.Transform` is now isn't exposed publically anymore.







Handle top-level fragments
2019-10-19T08:00:25+00:00

Eugen Wissner
belka@caraus.de

2019-10-19T08:00:25+00:00

c7d5b02911380583ea8ca4bfc600f533658ab16f

Fixes #17.





Fixes #17.







Inline fragments without type
2019-10-11T21:28:55+00:00

Eugen Wissner
belka@caraus.de

2019-10-11T21:28:55+00:00

37254c8c9532794ed41570ef8c646c41e7044f2c

Fixes #11.





Fixes #11.







Support inline fragments on types
2019-10-08T07:03:07+00:00

Eugen Wissner
belka@caraus.de

2019-10-07T19:03:07+00:00

856efc5d256449d9282f6547bb5f677d0a7fe482












Introduce hspec-megaparsec
2019-09-27T08:50:38+00:00

Eugen Wissner
belka@caraus.de

2019-09-27T08:50:38+00:00

eb98c3625866d6dbdf8d0f7943f6ebf55799bd57

Fixes #13.





Fixes #13.







Add pending inline fragment tests
2019-09-13T18:33:39+00:00

Eugen Wissner
belka@caraus.de

2019-09-13T18:33:39+00:00

c075a41582279be2ed1f2b5d5c758ab14d664770












Deprecate enum, enumA, wrappedEnum, wrappedEnumA
2019-09-01T01:16:27+00:00

Eugen Wissner
belka@caraus.de

2019-09-01T00:53:15+00:00

63d4de485d3cd96c00480dfe2e5a6cb320d520c7

These functions are from Language.GraphQL.Schema.
There are actually only two generic types in GraphQL: Scalars and objects.
Enum is a scalar value. According to the specification enums may be
serailized to strings. And in the current implementation they used
untyped strings anyway, so there is no point to have differently named
functions with the same implementation as their scalar counterparts.





These functions are from Language.GraphQL.Schema.
There are actually only two generic types in GraphQL: Scalars and objects.
Enum is a scalar value. According to the specification enums may be
serailized to strings. And in the current implementation they used
untyped strings anyway, so there is no point to have differently named
functions with the same implementation as their scalar counterparts.