James Bellenger

discuss: undeprecate setting data fetchers directly on fields

1

We rely pretty heavily on being able to assign a data fetcher to a field at the point that we are generating it, in part because that's what our previous...

Promise.all context propagation

1

Async-listener will propagate contexts through Promise.all, which is different behavior from similar functionality in the domain module. It's not 100% clear to me that this is a bug, though it...

add support for pagination

6

Implement api pagination. The semantics are: - if any single page request fails, reject the entire request - callbacks passed to `Client.request` will be called once the merged result -...

`Releases.files` does not return all results when a release contains over 100 files. This appears to be due to missing support for Sentry API [pagination](https://docs.getsentry.com/hosted/api/pagination/).

3.13 Directive validation edits

7

The Validation section for Directive types is a little out of step with the validation sections for the other types. In particular, while the grammar definition of Directive requires one...

initial test case

2

This test case fails with: ``` Condition not satisfied: typeB.sourceLocation.sourceName == "b" | | | | | | a false | | 1 difference (0% similarity) | | (a) |...

validate constant directive values

3

Consider this query, which uses a variable in a directive that is itself applied to a variable definition: ```graphql query ($v:Int @dir(arg:$v)) { __typename } ``` The [spec's grammar for...