graphql/src/Language/GraphQL/Schema.hs, branch v0.6.0.0 GraphQL implementation in Haskell. Add a reader instance to the resolvers 2019-11-23T08:49:12+00:00 Eugen Wissner belka@caraus.de 2019-11-23T08:49:12+00:00 587aab005ed1e4e9bd8966d44ff878891cbc8ce7 The Reader contains a Name/Value hashmap, which will contain resolver arguments. 
The Reader contains a Name/Value hashmap, which will contain resolver
arguments.
Rewrite selections into a Sequence. Fix #21 2019-11-16T10:41:40+00:00 Eugen Wissner belka@caraus.de 2019-11-16T10:41:40+00:00 7b92e5bcfded2a592b9be25d0865d26320421570 






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.







Remove deprecated functions and aliases
2019-10-25T07:07:45+00:00

Eugen Wissner
belka@caraus.de

2019-10-25T07:07:45+00:00

51d39b69e83a9e258c7b6ee4b81dcfcb3063e6fc












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












Fix haddoc warnings
2019-09-20T06:47:14+00:00

Eugen Wissner
belka@caraus.de

2019-09-20T06:47:14+00:00

2b5c719ab06b28aef8a242ffbbda256191e32655

Fix #14.





Fix #14.







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.







Deprecate Language.GraphQL.Execute.Schema
2019-08-30T05:26:04+00:00

Eugen Wissner
belka@caraus.de

2019-08-30T05:26:04+00:00

22313d05df7d96cd8106bc42f787bc74d74596de

It is not a schema (at least not a complete one), but a resolver list,
and the resolvers should be provided by the user separately, because the
schema can originate from a GraphQL document. Schema name should be free
to provide a data type for the real schema later.





It is not a schema (at least not a complete one), but a resolver list,
and the resolvers should be provided by the user separately, because the
schema can originate from a GraphQL document. Schema name should be free
to provide a data type for the real schema later.







Make all exports explicit
2019-07-14T03:58:05+00:00

Eugen Wissner
belka@caraus.de

2019-07-14T03:58:05+00:00

f3b8d9b74ccd24521a9f15fe4bd47ab30830abfb












Constrain the resolvers with MonadIO
2019-07-08T08:15:47+00:00

Eugen Wissner
belka@caraus.de

2019-07-08T08:15:47+00:00

61879fb12437302d6b14e0e0297e3a8742d91f8b

This replaces the most usages of MonadPlus, which is not appropriate for
the resolvers, since a resolver is unambiguously chosen by the name (no
need for 'mplus'), and the resolvers are often doing IO.





This replaces the most usages of MonadPlus, which is not appropriate for
the resolvers, since a resolver is unambiguously chosen by the name (no
need for 'mplus'), and the resolvers are often doing IO.