Skip to content

Make schema coordinates a collective work #1800

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 17, 2025
+2 −2
Merged

Make schema coordinates a collective work #1800

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions agendas/2025/07-Jul/17-wg-secondary-eu.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,9 +129,9 @@ who could not make the primary meeting time.
- Really important!
1. Discussion: [Remove fragmentSpreadName from visitedFragments after visit](https://github.com/graphql/graphql-spec/pull/1045) (10m, Benjie)
1. Discussion: service capabilities syntax (10m, Benjie)
1. Schema coordinates may not include `{Ignored}` (5m, Martin)
1. Schema coordinates may not include `{Ignored}` (5m, Martin, Mark, Benjie)
- https://github.com/magicmark/graphql-spec/pull/2
- Do we want to be explicit about this?
- If yes, should this be in section 2. or somewhere else (Section 3?)?
1. Anything else missing for schema coordinates? (5m, Martin)
1. Anything else missing for schema coordinates? (5m, Martin, Mark, Benjie)
- https://github.com/graphql/graphql-spec/pull/794