-
Notifications
You must be signed in to change notification settings - Fork 379
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
support for XmlEnumAttribute specifiying custom names for enum members #986
support for XmlEnumAttribute specifiying custom names for enum members #986
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much for the PR!
Looks good! I left a comment regarding the performance. Please take a look at that and we can get this PR merged shortly
hi Anders, wow, I didn't expect, that a Linq query with a join would have better performance, than just looping and querying for single members. But yeah, the difference is huge, so I've changed the implementation to your proposal. Maybe an additional question - I've seen, that wsdl generation with XmlSerializer currently doesn't support SOAP fault contracts. Do you know, if someone is already on it? Otherwise I could try to implement it. Best regards, |
Yeah, it's the query per member that's killing perf. That same "pattern" has caused me lots of headache over the years 😅
Not to my knowledge. You are more than welcome to give it a go 😄 |
Merged! Thanks again! |
OK, I'll give it a try :-) Could you maybe publish the new package version? This XmlEnum stuff is really needed, otherwise I'd have an enum with one-letter-members in my current project, which is terrible 😄 |
Done. A new version should be available on nuget in a couple of minutes |
Feature request: support for XmlEnumAttribute to be able to specifiy custom names for enum members
for the example enum, used in test CheckEnumWithCustomNamesXmlSerializedWsdl
the expected output would be