Benjie
If you use a true resolver the schema becomes impure and certain optimisations cannot be used; but there should be no need: pass the parent arg, fieldArgs, and context() into...
cc @JoviDeCroock @yaacovCR
I've partially addressed this in https://github.com/graphql/graphql.github.io/pull/1958 - most of the links work again now (by redirecting to the /docs/ URL) but we still need to solve the internal links issue...
The reason that the `Query`, `Mutation` and `Subscription` types are considered object types, is because they _are_ object types. They are defined in exactly the same way, they operate in...
Another way to think about it is in terms of graph traversal (see [my blog post on this topic](https://benjie.dev/graphql/traversal)) - the `Query` type effectively represents the "node" in the graph...
Awesome - would be great to have your help! The graphql-js.org website is currently being rewritten - if you'd like to get involved in that I encourage you to talk...
If you can keep the changes small (but ensure that the surrounding text is correctly adjusted) please do go ahead :) AFAIK no-one else is scheduled to make these specific...
I'd go with option 1 for now, seems the ~~safest~~ least likely to break CI flows :+1:
> I feel guidance with lots of caveats > no guidance. Agreed; but I'd prefer that our guidance was "don't do that, and here's why and what you might consider...
I think adding something to the docs saying something along the line of the following would be good :+1: > While `bun` is not an officially supported runtime for Graphile...