Max DeCurtins

This would be extremely useful for me, especially in adding custom rules where I want to emit a warning instead of an error, so I can raise potential problems with...

Hi @cjoudrey I'm considering taking a crack at this and I'm getting acquainted with how everything is run before I make any changes. This could potentially be implemented using the...

I'd also like to see additional characters allowed specifically in enum members, e.g. `+` (as well as `-` and `/`). (I'm less concerned with type names, but maybe someone else...

> There is a generic principle that should be followed: internal 'code' names and user visible labels are completely different set of tokens, and live in separate universes, and should...

I agree that this should be supported in some fashion. Personally, I'm not very convinced by the argument in https://github.com/graphql/graphql-spec/issues/500 that allowing field inheritance from implemented interfaces reduces schema readability...

+1 Exact enums would be a useful construct, particularly in the absence of generics.

Just coming here to say this would be very useful. We don't have a federated schema, but for `graph publish` it would be great to supply a file glob instead...

Same problem with `@apollo/react-hooks: "~3.1.5"` and `apollo-client: "~2.6.4"`. I initially tried to use `useLazyQuery` for my case but I could never get it to show the `loading` state; it was...

I would also be interested in this. While I do eventually think it could be useful to lint against a schema, my current use case is that I want to...