| Age | Commit message (Collapse) | Author |
|
It makes using variables with queries more approachable, but some work
still has to be done.
- The type `Subs` should be renamed and moved out of `Schema`, together with
`AST.Core.Value` probably.
- Some kind of conversion should be possible from a user-defined input
type T to the Value. So the final HashMap should have a type like
`HashMap name a`, where a is an instance of a potential typeclass
InputType.
|
|
|
|
Large parts of the schema aren't exported publically. They will be made
public during writing the parser.
Fixes #6.
|
|
|
|
|
|
Fixes #10.
|
|
|
|
|
|
Just to roughly follow the structure of the reference implementation.
|
|
Language.GraphQL.AST.Transform is an internal module. Even though it
works with the AST, it is a part of the execution process, it translates
the original parser tree into a simpler one, so the executor has less
work to do. Language.GraphQL.AST should contain only the parser and be
independent from other packages, so it can be used on its own.
|
|
Fixes #24.
|
|
Fixes #30.
|
|
Fixes #28
|
|
The Reader contains a Name/Value hashmap, which will contain resolver
arguments.
|
|
|
|
Fixes #25.
|
|
|
|
|
|
Fix #19.
|
|
... without forward lookup.
|
|
The reader contains variable substitution functions and fragments.
|
|
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.
|
|
Since the transform tree can already find some errors, it may fail here
and there. Almost all functions return a Maybe to signalize an error.
Will be replaced with an Either of course.
|
|
Fixes #20.
|
|
|
|
Fixes #17.
|
|
Fixes #11.
|
|
|
|
Fixes #16. Deprecates:
- Language.GraphQL.AST.Arguments
- Language.GraphQL.AST.Directives
- Language.GraphQL.AST.VariableDefinitions
|
|
Fixes #15.
|
|
Fix #14.
|
|
|
|
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.
|
|
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.
|
|
Mostly basic documentation. Fixes #4.
|
|
|
|
|
|
Fixes #2.
|
|
|
|
|
|
|
|
... to distinguish between minified and pretty printing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|