Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handling of case sensitive simple types #154

Open
matzipan opened this issue Dec 13, 2023 · 1 comment
Open

Handling of case sensitive simple types #154

matzipan opened this issue Dec 13, 2023 · 1 comment

Comments

@matzipan
Copy link

In this XSD, the following type exists:

<xsd:simpleType name="yesNoType">
   <xsd:restriction base="xsd:string">
      <xsd:enumeration value="YES"/>
      <xsd:enumeration value="yes"/>
      <xsd:enumeration value="NO"/>
      <xsd:enumeration value="no"/>
   </xsd:restriction>
</xsd:simpleType>

Because xsd-parser tries to change the case of the enum label from YES to Yes and from yes to YES, they clash.

xsd-parser could try to detect such cases and keep the case.
lkirkwood added a commit to lkirkwood/xsd-parser-rs that referenced this issue Apr 20, 2024
@lkirkwood
Stop pascalizing enum case name to avoid clashes
3f4485d 
Pascalizing enum case names in restrictions can cause clashes (see lumeohq#154)
lkirkwood added a commit to lkirkwood/xsd-parser-rs that referenced this issue Apr 20, 2024
@lkirkwood
Stop pascalizing enum case name to avoid clashes
2a97fcd 
Pascalizing enum case names in restrictions can cause clashes (see lumeohq#154)
@lkirkwood lkirkwood mentioned this issue Apr 20, 2024
Open
@lkirkwood
Copy link
Contributor

#162 addresses this but it is a breaking change so it might not get merged. It should fix this issue for you though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matzipan @lkirkwood