Open Salamit opened 4 years ago
Solution would be to throw an error with an explicit schema when creating the graphql schema.
Schema keys must respect the Graphql "Name" pattern defined in the standard https://graphql.github.io/graphql-spec/June2018/#sec-Names
@eric-burel
Hi Eric, I am new to VulcanJS, but I want to join in the development.
For this issue, as I understand, the fix is to
Would you help to verify the above rephrasing? That will help to build some confidence for me to go further with the implementation.
Hey @eric-burel can I work on this issue?
Hi, the Meteor version is deprecated so it's ok to contribute but it's better to work on Vulcan Next/ Vulcan NPM: https://vulcan-docs.vercel.app/
In response to @eric-burel asking me to open an issue, schema files allow for numbers as keys but numbers as keys aren't allowed in GraphQL fragments. See the below example.