Seperate ClrNameSource Setting to use individual settings for class name vs. property names
Opened this issue · 0 comments
JohnBergman commented
Not a bug, but can you separate the ClrNameSource setting into two so that there is a little more fine grained control over the naming of classes vs. properties.
(You might also want to add this to the documentation page, I dug through the code to find it, and it is awesome!)
Also it would he helpful if the filename matched whatever was selected in the ClrNameSource as well, when I changed mine to RawAlias, the filenames were still cased as if the default class name was generated.