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.

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

extending simpleType and adding attribute named value #221

Closed
lyle-janrain opened this Issue Jul 31, 2013 · 0 comments

Comments

Projects
None yet
1 participant
@lyle-janrain

steps

  1. compile a complex type that extends xs:string and adds an attribute named value.
    <xs:complexType name="FieldOption">
        <xs:simpleContent>
            <xs:extension base="xs:string">
                <xs:attribute name="disabled" type="xs:string" default="string" use="optional"/>
                <xs:attribute name="value" type="xs:string" use="optional"/>
            </xs:extension>
        </xs:simpleContent>
    </xs:complexType>

problem

It generates value twice.

case class FieldOption(value: String,
  disabled: String,
  value: Option[String] = None)

expectation

  1. rename the second value.

original

This may need to be broken into several issues. The code generated from the schema is not compiling.

Here's the schema:
https://gist.github.com/lyle-janrain/542f76bee25fd41227d8

Here's the generated flow.scala (flow is my chosen package name):
https://gist.github.com/lyle-janrain/920e6cd906f919d6138a

Here's the generated xmlprotocol.scala:
https://gist.github.com/lyle-janrain/e3b3546d7d2f7464e62d

This gist has all the errors: https://gist.github.com/lyle-janrain/2739a17716de23a96787

Seems like there may be multiple unrelated issues. The thing about FieldOption is one, the stuff about p1 is another, and the foo thing, I'm not sure.

This was referenced Jul 31, 2013

@eed3si9n eed3si9n closed this in 0e1ca96 Aug 18, 2013

eed3si9n added a commit that referenced this issue Sep 13, 2013

eed3si9n added a commit that referenced this issue Nov 8, 2014

eed3si9n added a commit that referenced this issue Jul 7, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment