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-11-05] Give feedback on the Schema Coordinates suggested GraphQL Spec Appendix #542

Closed
benjie opened this issue Nov 8, 2020 · 2 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 Nov 8, 2020

  • Mark: as a reminder, the elevator pitch: in various GraphQL projects we need to refer to components of the schema, e.g. field name on a type, we commonly write this as e.g. User.name. There's no official convention, but tooling uses this convention, so this RFC tries to standardize and extend this syntax (e.g. referring to arguments)
  • Great reviews so far, especially from Ivan
  • What's the next steps?
  • Lee: ACTION - everyone: take a look at the appendix and reply with detailed feedback

graphql/graphql-spec#746


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

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

benjie commented Dec 4, 2020

@magicmark Please could you comment on this issue so that I can assign you? A simple 👍 will suffice 😉

(It was noted in the WG yesterday that when a task is for everyone, it should be assigned to the person spearheading the effort to solicit feedback.)

@magicmark
Copy link
Contributor

@benjie sorry I totally missed this!

Yes chef!

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
None yet
Development

No branches or pull requests

3 participants