v.1.0.0 and property casing
See original GitHub issueHi!
I’ve just tried 1.0.0
and it does exactly what I want for custom file and model naming - excellent work 😄 However, it seems like propertyCasing
is gone, which is something I was relying on (I’m using slonik
configured to auto convert property names to camel case). Is there a way for me to implement that same functionality somehow using 1.0.0
?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
MSBuild reference for .NET SDK projects - Microsoft Learn
Reference for the MSBuild properties and items that are understood by the .NET SDK. ... <Version>1.0.0</Version> <Authors>John Doe</Authors> ...
Read more >VSCode linting not working - Cannot find module 'eslint-plugin ...
Tell us about your environment ESLint version: 6.6.0 ... 13:9 warning Property name "XXX" is not PascalCase vue/name-property-casing.
Read more >WIPO Sequence Suite
A User Manual PDF, WIPO Sequence version 1.1.0 User Manual is provided to assist applicants in generating their compliant sequence listings.
Read more >c# - Can I automatically increment the file build version when ...
If I look up the properties of say C:\Windows\notepad.exe , the Version tab gives "File version: 5.1.2600.2180". I would like to get these...
Read more >Sub-Properties and Container Keys - PTC Support
Many configuration properties in the component configuration include sub-properties. A sub-property is a property contained within another property, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Works wonders! Thank you @kristiandupont ! 👏
Ok, this is fixed in 1.1.0. Let me know if it works!