Enum naming conflict

[sashkent3]

Consider the following simple schema

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Root">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="UniqueName1">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Value">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Status">
                    <xs:simpleType>
                      <xs:restriction base="xs:string">
                        <xs:enumeration value="Rejected"/>
                        <xs:enumeration value="Completed"/>
                      </xs:restriction>
                    </xs:simpleType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="UniqueName2">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="Value">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="Status">
                    <xs:simpleType>
                      <xs:restriction base="xs:string">
                        <xs:enumeration value="Pending"/>
                        <xs:enumeration value="Approved"/>
                      </xs:restriction>
                    </xs:simpleType>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
</xs:schema>

And an example XML

<Root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <UniqueName1>
    <Value>
    	<Status>Completed</Status>
    </Value>
  </UniqueName1>
  <UniqueName2>
    <Value>
    	<Status>Pending</Status>
    </Value>
  </UniqueName2>
</Root>

According to tools like https://www.liquid-technologies.com/online-xsd-validator, the pair is valid. However, there's a problem with the output of xsdata. It generates a single:

class ValueStatus(Enum):
    REJECTED = "Rejected"
    COMPLETED = "Completed"

...and uses it for both Root.UniqueName1 and Root.UniqueName2. This is incorrect, as a distinct Status enum should be generated for the Root.UniqueName2.

[sashkent3]

This seems similar to #375

[sashkent3]

Setting UnnestClasses to true seems to help.

[tefra]

Confirmed, thanks for reporting @sashkent3