We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
pk_columns
Server Version: 2.21
OSS
Upgrading Hasura from 2.16.0 to 2.21.0 broke the mutations, since the pk_columns in default mutations are referenced as camelCase pkColumns.
pkColumns
There is no mention in the release notes about this change.
Furthermore, a minor version upgrade should not have a breaking change.
A minor version upgrade should not have breaking change in the API.
Degrading back to 2.16.0
breaking-change, camecase, snakecase, pk columns
The text was updated successfully, but these errors were encountered:
Hey there were some fixes related to the naming conventions feature introduced in v2.21.
v2.21
"Fix graphql-default naming convention bugs (#9426, #9430)"
Can you confirm if you were using the graphql-default naming convention? That might explain this behaviour
graphql-default
Sorry, something went wrong.
@rikinsk Yes, we have graphql-default naming-convention.
No branches or pull requests
Version Information
Server Version: 2.21
Environment
OSS
What is the current behaviour?
Upgrading Hasura from 2.16.0 to 2.21.0 broke the mutations, since the
pk_columns
in default mutations are referenced as camelCasepkColumns
.There is no mention in the release notes about this change.
Furthermore, a minor version upgrade should not have a breaking change.
What is the expected behaviour?
A minor version upgrade should not have breaking change in the API.
How to reproduce the issue?
pk_columns
in version 2.16.0pkColumns
.Any possible solutions/workarounds you're aware of?
Degrading back to 2.16.0
Keywords
breaking-change, camecase, snakecase, pk columns
The text was updated successfully, but these errors were encountered: