-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Camel case arguments are not working with Func plugin #63
Comments
Hi there! Thanks for the issue. I have just created a pull request that should fix this : #64 . Arguments now automatically aliases arguments when the stylers version doesn't match the original field_name Here: class Arguments(BaseModel):
user_id: str = Field(alias="userId") As this may introduce some inconveniences when parsing arguments, this PR also introduce a new operations - type: turms.plugins.operations.OperationsPlugin
arguments_allow_population_by_field_name: True #default is false class Arguments(BaseModel):
user_id: str = Field(alias="userId")
class Config:
allow_population_by_field_name= True Which allows population like this: "QueryName.Arguments(user_id=3)" on to op "QueryName.Arguments(userId=3)" Feel this is not the smoothest solution though, any ideas on that? |
Hi! Thank you for tackling this issue so quick. What's the downside of having |
Hi @DGolubets, i am closing this issue now, which i should have done a while ago :D hope everything still works for you, |
Hi,
It seems that there is some inconsistency in arguments casing when using the Func plugin.
I use the following config:
I got this Arguments class generated:
But my query uses
$userId
.The text was updated successfully, but these errors were encountered: