-
Notifications
You must be signed in to change notification settings - Fork 731
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
Add casing strategies for property names #2738
Comments
Are there any updates on this issue? Our team is waiting for this to be in before we update our pod |
No updates @emily-discz. It's also not scheduled for any particular minor release yet, just in the list of future minor releases. We're always willing to accept PRs that help get the work done. |
Any updates on this? |
@iDylanK No more new updates since @calvincestari comment on May 31, still not currently scheduled into any particular minor release. |
Just to add a data point, this is currently blocking us from updating to later versions of the framework. |
Same for our company. |
That is good to know. This has been pretty low on our priority list, but we will reassess that during our next planning meeting. Thanks for the feedback. |
also needed from my company |
This is now available in the 1.4.0 release |
Use case
I created a new issue for this feature request since we closed #2641.
The gist is to provide casing strategies for other parts of generated code, such as fields, similar to the current option for enums.
Describe the solution you'd like
No response
The text was updated successfully, but these errors were encountered: