grackle
grackle copied to clipboard
typelevel
Grackle: Functional GraphQL for the Typelevel stack
Currently embedded subobjects are assumed to be non-null. There are workarounds for situations which require nullability, but these aren't ideal and it would be better to provide first-class support.
Current coverage of the [GraphQL Specification, June 2018](https://graphql.github.io/graphql-spec/June2018/). - [x] 2 Language - [x] 2.1 Source Text - [x] 2.1.1 Unicode - [x] 2.1.2 White Space - [x] 2.1.3 Line...
This would support structured non-schema attributes.
- [x] Rename master to main (#130) - [x] Get rid of `NoType` (#129) - [x] ~~Switch from `NullableType` to `NonNullType`~~ (#33) - [x] Unify fields and attributes - [x]...
In the meantime a similar effect can be achieved with a view.
In the meantime a similar effect can be achieved using a view.
Tracing is always available if you're using Skunk, so we can replace SkunkMonitor with something that records events in context.
Not quite published yet, but imminent: https://github.com/graphql/graphql-spec/pull/871 Changelog here: https://gist.github.com/leebyron/b804daea5abd624e638708bfbb731804.
Define a method on `SqlMapping` that verifies referenced columns exist and are declared with compatible types and nullity.