Benjie comments

Results 1618 comments of


                                            Benjie

Adaptor for fastify@v5

Please feel free to submit an adaptor! Probably you just need to copy the v4 one and replace all instances of v4 with v5 and it’ll probably work 🤷‍♂️

No validation rule exists to assert mutation/subscription operations exist in the schema

I agree with the need for this. Would you like to work on it? (You might consider applying for a small [GraphQL Grant](https://graphql.org/community/foundation/community-grant/) if you need some financial support.) I...

No validation rule exists to assert mutation/subscription operations exist in the schema

Moving the RFC label to the PR.

No validation rule exists to assert mutation/subscription operations exist in the schema

Closing in favour of the PR: https://github.com/graphql/graphql-spec/pull/1098

Publish to JSR

I've requested the `@graphql` scope at JSR.

Figure out a way to prevent steps depending on "opaque" steps

This should also be used when handing from plan-space to resolver-space; e.g. if you have a `const $user = users.get({ ... })` and then you have a resolver on the...

Figure out a way to prevent steps depending on "opaque" steps

Punted to V6.

[RFC] Type system ordering of: object interfaces, directive arguments, input object fields, enum values

> The prior presence of “set” to me unambiguously implied unordered. I don't think the term "set" itself implies ordered or unordered, "set" is independent of ordering. For example in...

[RFC] Type system ordering of: object interfaces, directive arguments, input object fields, enum values

I've added a note to the beginning of the spec :+1:

[RFC] Type system ordering of: object interfaces, directive arguments, input object fields, enum values

@leebyron I've changed list, set and map into definitions and have also changed the final non-normative note into a normative statement since it uses the word `should` (equivalent to `we...