RFC for introspection field for spec information

[dblandin]

RFC for introspection field for spec information

assignee: @eapache & @andimarek
source: GraphQL Working Group Meeting 2019-07-03

[eapache]

Myself (@eapache) and @andimarek are working on this.

[eapache]

It's not ready for review, but I'm cutting a very rough first draft of the spec changes at https://github.com/eapache/graphql-spec/tree/custom-scalar-formats.

[benjie]

@eapache Do you think we should address versioning of these custom scalar specification documents? I think it's mostly beyond the scope of the spec, except maybe it should state that non-trivial ("functionally significant"?) changes to the specification document should result in a new specificationUri? E.g. JSON -> JSON5 would break previous parsers, so should require a new URI? Presumably this also would mean that changing the specificationUri would be a breaking change.

[eapache]

That's a really good point, I'll work that in.

[eapache]

This action item is effectively done, the RFC exists and is nicely in progress graphql/graphql-spec#635

[dblandin]

This action item is effectively done, the RFC exists and is nicely in progress graphql/graphql-spec#635

Awesome! Going to go ahead and close this issue 🎉