You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that if I use {snake_case} in my translation strings, that the corresponding method does not apply camel case to the method's named parameters. For example, given the following translation string:
{
"visit_status": "{status_text} at {when}"
}
I would expect the following method signature to be generated with the named parameter statusText having camel case applied.
StringvisitStatus({requiredObject statusText, requiredObjectwhen}) =>'$statusText at $when';
However, the following method signature is generated where the snake case has not been converted to camel case.
StringvisitStatus({requiredObject status_text, requiredObjectwhen}) =>'$status_text at $when';
Thank you for this helpful package.
I've noticed that if I use
{snake_case}
in my translation strings, that the corresponding method does not apply camel case to the method's named parameters. For example, given the following translation string:I would expect the following method signature to be generated with the named parameter
statusText
having camel case applied.However, the following method signature is generated where the snake case has not been converted to camel case.
My
build.yaml
file is:The text was updated successfully, but these errors were encountered: