Martin Bonnin

> `experimentalReason` That was another question I had actually. I don't really see a use case for `experimentalReason`. All my use cases will most likely say something like "this field...

@benjie Sure thing! Pull request is there https://github.com/graphql/graphql-wg/pull/964.

If we're going the full Kotlin-like route, we could even think of adding directive usages to directive definitions: Specified directive: ```graphql directive @optIn ``` User schema for something like [Github...

I've added a RFC at https://github.com/martinbonnin/graphql-wg/blob/opt-in-features/rfcs/OptInFeatures.md. This is still pretty much a work in progress but it'll be easier to read for someone that just bumps into this thread or...

Linking [the ImplicitInheritance RFC](https://github.com/graphql/graphql-wg/blob/main/rfcs/ImplicitInheritance.md) here as it seems (loosely at least?) related to this issue? If: 1. GraphQL allowed for implicit inheritance 1. Introspection only returns each type "own" fields...

Closing in favor of https://github.com/graphql/graphql-wg/pull/1006

Could the non-nullability information somehow be made available as schema extensions (schema level) in addition to query fields (query level)? From my understanding, a lot of the nullability friction comes...

In theory, you could have an arbitrary number of nested `Lists` where each item type could be nullable: ```graphql type Transformation { # here everything is nullable rotationMatrix: [[Int]] #...

+1 to this. The tooling is improving regularly and can help with this. Also the argument that [SDL should favor reading reading over writing](https://github.com/graphql/graphql-spec/issues/500#issuecomment-426146328) could also be turned the other...

Should we add `.graphqls` as an extra extension for schema files containing only type system definitions or extensions? It's technically all the same language (GraphQL) but tools such as Apollo...