If multiple elements with different names are of the same complexType, their XML name tag conflicts with the XMLName field of the struct defined for that complexType:
Example for <xs:complexType name="typeUnderTest">:
Now anotherTopLevelElement, elmComplexContent and elmComplexType all conflict with topLevelElement which was selected as the XMLName field tag of type TypeUnderTest struct.
This issue was first addressed with PR #109 (issue #73) in commit, but without addressing the scenario described here.
If multiple elements with different names are of the same complexType, their XML name tag conflicts with the XMLName field of the struct defined for that complexType:
Example for
<xs:complexType name="typeUnderTest">
:generates this Go code (header info omitted):
Now
anotherTopLevelElement
,elmComplexContent
andelmComplexType
all conflict withtopLevelElement
which was selected as the XMLName field tag oftype TypeUnderTest struct
.This issue was first addressed with PR #109 (issue #73) in commit, but without addressing the scenario described here.