Schema Coordinates
At a glance​
- Identifier: #794
- Stage: RFC2: Draft
- Champion: @magicmark
- PR: Schema Coordinates
- Related:
- SchemaCoordinates (Schema Coordinates)
Timeline​
- 4 commits pushed on 2024-12-10:
- Added to 2021-06-03 WG agenda
- Mentioned in 2021-06-03 WG notes
- Commit pushed: Minor algo variable name refinements on 2021-04-22 by @leebyron
- 7 commits pushed on 2021-04-16:
- Commit pushed: standalone on 2021-04-15 by @leebyron
- Commit pushed: Simplify examples on 2021-04-14 by @leebyron
- 2 commits pushed on 2021-04-13:
- Mentioned in 2021-03-04 WG notes
- Commit pushed: Update Section 3 -- Type System.md on 2021-01-07 by @magicmark
- Added to 2021-01-07 WG agenda
- Mentioned in 2021-01-07 WG notes
- Commit pushed: - Add PR feedback on 2021-01-04 by @magicmark
- Commit pushed: enumName -> enumValueName on 2020-11-28 by @magicmark
- Commit pushed: Apply suggestions from code review on 2020-11-23 by @magicmark
- Commit pushed: Tweak example table wording on 2020-11-22 by @magicmark
- Commit pushed: implement PR suggestions on 2020-11-21 by @magicmark
- Spec PR created on 2020-11-18 by magicmark
- Commit pushed: Update schema coordinates spec edit on 2020-11-18 by @magicmark
- Commit pushed: Add Schema Coordinates RFC on 2020-09-17 by @magicmark
👋
I've pulled out the proposed spec edits for Schema Coordinates (issue: https://github.com/graphql/graphql-spec/issues/735) into this PR.
(The RFC now lives in the original PR: https://github.com/graphql/graphql-spec/pull/746/files)
@leebyron you mentioned it might be possible to simplify the grammar - I played around a bit since the original PR, but I think I need some help here. What did you have in mind?
As suggested, tagging @eapache @mjmahone as additional reviewers as we had some good conversation in last WG meeting about this.
Thanks!