Fix simple content extension.

[ph777]

This PR extends autocomplete-xml package with ability to recognize simple content extension. For example when a simple type is extended with an attribute.

<xs:simpleType name="extendedType">
  <xs:extension base="xs:string">
    <xs:attribute name="myAttr" type="xs:string"/>
  </xs:extension>
</xs:simpleType>

The fix shoud work correcly for both standard simple types like xs:string and custom simples, e.g. string restrictions, etc.

Please review the PR and consider merging it to your package.

[pleonex]

Thanks for the changes!

[pleonex]

Are we parsing the simpleType node in parseComplexType? I think that node is only parsed in parseSimpleType, right?

[ph777]

We are not parsing simple type, but complex type with simple content. The simpleContent element can appear in complex type, e.g. when defining an element with string content (simple content) and an attribute:

<xs:complexType name="myType">
    <xs:simpleContent>
        <xs:extension base="xs:string">
            <xs:attribute name="name" type="xs:string" use="required"/>
        </xs:extension>
    </xs:simpleContent>
</xs:complexType>

[pleonex]

Oh, it makes sense now, thanks!

[pleonex]

What do you think about creating a global list of built-in types? Then we can check here against that list (and also in #48). As a start we can add to the list the most common built-in types:

• xs:string
• xs:decimal
• xs:integer
• xs:boolean
• xs:date
• xs:time

[ph777]

I agree that the way I distinguish between a built-in type and custom type is not perfect, but it is working fine for the usual cases. So I think it is a reasonable simplification.

If you want to include list of built-in types than I would suggest to make the list complete. To be perfect the namespace prefix would have to be checked too to distinguish between xs:string and my:string.

[pleonex]

Make sense, it will be implemented from a different issue from #49.