-
Notifications
You must be signed in to change notification settings - Fork 181
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
Invalid Chars #221
Comments
This is similar to #220. Ideally, you'd be able to provide custom replacements for individual characters and whole strings, so that e.g. you'd be able to replace the string Perhaps in addition to specifying individual replace directly in the CLI it would be nice to be able to specify a mapping file (JSON or TOML?). |
It would be great if the naming would be more suitable for periods (.) and hyphens (-) inside XSD complexType names. Currently Expect type names with periods and hyphens. Please substitute the C# class naming with underscores for periods and hyphens. |
Perhaps for now you can use the type name substitution feature ( |
This feature would be very useful when you have a lost of XSD files and a lot of classes are generated. |
@luissagasta This is the case with the new PascalCase naming scheme. Are you using the direct or legacy naming schemes? |
I am using direct naming schema |
Hi,
great library!
One suggestion for another feature: It would be great to be able to override the default replacements for invalid chars in the cli (https://github.com/mganss/XmlSchemaClassGenerator/blob/46da19544ce19a466d97ac5140da62865ef3f6e7/XmlSchemaClassGenerator/NamingExtensions.cs).
The text was updated successfully, but these errors were encountered: