Replies: 3 comments
-
I don't think a warning is necessary if we instead format field names to replace invalid characters. That is already done on slugs. I'd like to see what it breaks to do try it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Seems awesome Dan, I thought it was too hard to format. But if we CAN format it, that would be great. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Gonna convert this to a discussion and add it to our roadmap. Thanks for the discussions here! 👍 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Bug Report
GraphQL doesn't work with field names that have hyphens in them, This lead to me doing a database conversion and renaming all my fields to camelcase. This should be a warning in the TSConfig or something. Or ESLint or whatever is able to give a warning when using a field name with a hyphen or anything that would break GraphQL
Steps to Reproduce
Other Details
Beta Was this translation helpful? Give feedback.
All reactions