-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat: allow symbols as GraphQLSchema extension fields #3511
Conversation
✔️ Deploy Preview for compassionate-pike-271cb3 ready! 🔨 Explore the source changes: 10ba0fa 🔍 Inspect the deploy log: https://app.netlify.com/sites/compassionate-pike-271cb3/deploys/6230936702007b00093bc3fa 😎 Browse the preview: https://deploy-preview-3511--compassionate-pike-271cb3.netlify.app |
@IvanGoncharov supporting TypeScript 4.3 prevents supporting symbols as index keys (#3511) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@n1ru4l Symbols as extensions keys totally make sense.
Please add some basic tests.
As for ObjMap
I'm don't understand motivation for this change.
Can you please clarify it?
Thanks for clarification 👍 |
Flagging for v17 |
Supersedes #3511 This adds support for `Symbol` property keys on the extension property of AST nodes. Had to tweak `toObjMap` here to support symbol keys by adding `getOwnPropertySymbols` which is the only way to enumerate over them. --------- Co-authored-by: n1ru4l <[email protected]>
Part of v17 now |
Supersedes graphql/graphql-js#3511 This adds support for `Symbol` property keys on the extension property of AST nodes. Had to tweak `toObjMap` here to support symbol keys by adding `getOwnPropertySymbols` which is the only way to enumerate over them. --------- Co-authored-by: n1ru4l <[email protected]>
No description provided.