These are a few bugs I noticed while testing my latest PR and you can reproduce them with the wss.xsd from tests.
I don't see how they would be linked to my changes, so I'm opening this issue.
There are tons of enums in this XSD, but for some reason one causes an error. Class FieldDefinition has both a local enum IMEModeand a property with the same name, which of course is a C# error.
Inside ViewDefinition, member Query hides an inherited member but is not declared with new, that triggers a C# warnings.
Here again there are tons of new members in the codegen, not sure why this one is missed.
Conversely, member ID of SharedFieldDefinition is declared new although it doesn't hide anything, which is also a C# warning.
You'll notice that the backing XName field I created triggers the same warning but that's expected because it uses the same IsNew logic as the property itself.
These are a few bugs I noticed while testing my latest PR and you can reproduce them with the
wss.xsd
from tests. I don't see how they would be linked to my changes, so I'm opening this issue.There are tons of enums in this XSD, but for some reason one causes an error. Class
FieldDefinition
has both a local enumIMEMode
and a property with the same name, which of course is a C# error.Inside
ViewDefinition
, memberQuery
hides an inherited member but is not declared withnew
, that triggers a C# warnings. Here again there are tons ofnew
members in the codegen, not sure why this one is missed.Conversely, member
ID
ofSharedFieldDefinition
is declarednew
although it doesn't hide anything, which is also a C# warning. You'll notice that the backing XName field I created triggers the same warning but that's expected because it uses the sameIsNew
logic as the property itself.