graphql-js icon indicating copy to clipboard operation
graphql-js copied to clipboard

A reference implementation of GraphQL for JavaScript

Results 322 graphql-js issues
Sort by recently updated
recently updated
newest added

= The child interfaces must eventually resolve to a runtime object type. implements: #3253

PR: feature 🚀

Extracted from #1145: I very frequently use `visit` function in my work. However I never fully understood how it's working especially since entire `visitor.js` lacks typing. I managed to figure...

enhancement

This is the first step for a potential reintroduction of CommonJS alongside ESM that avoids the dual package hazard `instanceOf` issues. ~~In addition, I think it would make sense to...

# Feature requests Deno was released a few days ago, is there any plan to support it? https://deno.land/v1

enhancement

Currently, query resolvers for Array types can return not only JavaScript arrays, but any iterable. However, *async* iterables are not (yet) supported. Since GraphQL.js supports async resolvers and iterables, it...

This draft PR shows what I'm currently working on. It passes tests but fails due to lower coverage. I will try to split it into smaller commits with proper descriptions...

This is a backport of ~#3529~ #3651 to the `15.x` branch that fixes #3528. Full credit to @asztal for identifying the fix and submitting the original PR.

PR: bug fix 🐞

This is a backport of ~#3529~ #3651 to the `16.x` branch that fixes #3528. Full credit to @asztal for identifying the fix and submitting the original PR.

PR: bug fix 🐞

### Motivation Checking a string key on an array is not valid, correctly yielding a warning on a TS branch I'm playing in. Narrow the type with Array.isArray instead. ###...

New Spec PR: https://github.com/graphql/graphql-spec/pull/1098 Old Spec PR: https://github.com/graphql/graphql-spec/pull/947 Original issue raised by @benjaminjkraft : #3592

spec RFC