Skip to content
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.

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

[2020-07-02] Require Argument Uniqueness #505

Closed
benjie opened this issue Oct 1, 2020 · 7 comments
Closed

[2020-07-02] Require Argument Uniqueness #505

benjie opened this issue Oct 1, 2020 · 7 comments
Assignees
Labels
Action item 🎬 Ready for review 🙌 Action Item issues are reviewed and closed during Working Group meetings.

Comments

@benjie
Copy link
Member

benjie commented Oct 1, 2020

Ivan: validation for type system in chapter 3 requires uniqueness of type names, field names, etc; but we forgot to specify arguments were unique. It's not an editorial change, but pretty uncontroversial.
Lee: on the topic of having a process; we need to have a reference implementation before calling it final stage.
[...]
ACTION - Ivan - implement in GraphQL.js


Note: Action Item issues are reviewed and closed during Working Group
meetings.

@benjie benjie added this to To do in Actions 2020-07-02 via automation Oct 1, 2020
@IvanGoncharov
Copy link
Member

graphql-js is in feature freeze due to TS conversion.
I will work on it after 16.0.0 release.

@benjie
Copy link
Member Author

benjie commented Apr 8, 2021

@IvanGoncharov does this need a GraphQL Spec edit? If so it seems wise to slip this in before the spec cut.

@benjie benjie added the Ready for review 🙌 Action Item issues are reviewed and closed during Working Group meetings. label Apr 8, 2021
@benjie
Copy link
Member Author

benjie commented Apr 8, 2021

Adding Ready for review for us to discuss at the next WG; this might not be ready to actually close.

@benjie
Copy link
Member Author

benjie commented May 13, 2021

Note from the GraphQL WG: we're okay doing the spec changes for this (if any) after the spec cut if need be.

@benjie benjie removed the Ready for review 🙌 Action Item issues are reviewed and closed during Working Group meetings. label Jun 3, 2021
@benjie
Copy link
Member Author

benjie commented Jun 3, 2021

@IvanGoncharov to create the PR, hopefully by the next GraphQL Spec Working Group. Otherwise ask someone else to champion it.

@benjie benjie added the Ready for review 🙌 Action Item issues are reviewed and closed during Working Group meetings. label Jun 3, 2021
IvanGoncharov added a commit to IvanGoncharov/graphql-js that referenced this issue Jul 1, 2021
IvanGoncharov added a commit to IvanGoncharov/graphql-js that referenced this issue Jul 1, 2021
@IvanGoncharov
Copy link
Member

@IvanGoncharov
Copy link
Member

IvanGoncharov commented Jul 1, 2021

Sadly traveling today and can't champion it on WG.
@benjie Can you add it to the agenda, since it looks like it's totally non-controversial?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Action item 🎬 Ready for review 🙌 Action Item issues are reviewed and closed during Working Group meetings.
Projects
No open projects
Development

No branches or pull requests

3 participants