-
-
Notifications
You must be signed in to change notification settings - Fork 748
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
Changed argument name with NamingConventions is not found on mutations #3088
Comments
@PascalSenn had a quick look at your tests, but they only test if the arguments, types are correctly renamed in the schema? |
It looks as though this is still occurring in HotChocolate v13.7.0. I've setup a snake case naming convention and mutation conventions and running into it, @PascalSenn can this be re-opened? |
after upgrading to 13.8.1 only for one subgraph I get this I think is related to last fix for this issue, I will try to figure out what causes this only on this project (maybe some mutation input) EDIT: weird issue with a mutation (with conventions) having a non-nullable enum as input but also with a default value (which doesn't even make sense). After removing the default value all works fine. here is the StackTrace |
Describe the bug
When argument name in pure code first is changed with extending DefaultNamingConventions and GetArgumentMethod, it is not found on subsequent mutation execution, it returns that the old argument name is not found on the field
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should find the rewritten argument name which is
passwordRequestTokenInput
instead ofpasswordRequestTokenCommand
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: