-
Notifications
You must be signed in to change notification settings - Fork 115
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
hasura naming convention support #358
Comments
Same problem here... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
this problem still active for me |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Once the migration to go is complete this won't be a problem anymore |
Hi ser @dbarrosop , is there a timeline for when go migration will be complete? I would like to start a new project with nhost but this plagued my old project |
No, I am afraid we have no timeline. |
Hasura has a new feature naming convention, where you can set the style of naming to graphql-default. Nhost does not support that feature
The text was updated successfully, but these errors were encountered: