bug with min and maxOccurs when group or element is referenced twice

[HennoVermeulen]

Describe the bug
When the same group is referenced twice with different values for minOccurs/maxOccurs, the second xsdGroup gets the minOccurs/maxOccurs values of the first reference.

A similar issue exists for two references to the same element.

Expected behavior
When there is more than one reference to the same group or element, each solved reference should have the correct minOccurs/maxOccurs values.

Library Version
1.2.19

Additional context
Example for element:

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">

    <xs:element name="myElement" type="xs:string" />

    <xs:complexType name="complexType">
        <xs:sequence>
            <xs:element ref="myElement" minOccurs="1" maxOccurs="2"/>
            <xs:element name="otherElement" type="xs:string"/>
            <xs:element ref="myElement" minOccurs="3" maxOccurs="unbounded"/>
        </xs:sequence>
    </xs:complexType>

</xs:schema>

I think the solution for this is to also compare minOccurs/maxOccurs values when comparing an unsolved element with a concrete element.

I made a pull request with this solution and unit tests showing the issue: #79

[lcduarte]

This one I've made a small adjustment to work regardless of the type in the compareMinMaxOccurs method, but the results should be the same as the tests are still working.

This one was also deployed in the version 1.2.20.

[HennoVermeulen]

Thank you very much! The issue is indeed solved by using version 1.2.2.0.