Skip to content

Commit

Permalink
Add empty price settings group in XSD
Browse files Browse the repository at this point in the history
I did a bit of code digging but couldn't figure out why the price
component definition did not have any valid/configured child nodes for
<settings> whatsoever. I decided that the best route would be to add
blank groups with the proper labels, so that the actual validation
results remain unchanged, but the skeleton now exists for future
developers to add valid configuration.
  • Loading branch information
neillrobson committed May 11, 2018
1 parent 2d75f25 commit b32a33a
Showing 1 changed file with 24 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,31 @@
<xs:complexType name="componentPrice">
<xs:sequence>
<xs:group ref="configurable" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="settings" minOccurs="0" maxOccurs="1">
<xs:complexType>
<xs:choice maxOccurs="unbounded" minOccurs="0">
<xs:group ref="componentPriceSettings"/>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attributeGroup ref="ui_element_attributes"/>
</xs:complexType>

<xs:complexType name="formElementPrice">
<xs:sequence>
<xs:element name="settings" minOccurs="0" maxOccurs="1">
<xs:complexType>
<xs:choice maxOccurs="unbounded" minOccurs="0">
<xs:group ref="componentPriceSettings"/>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>

<xs:group name="componentPriceSettings">
<xs:choice>
</xs:choice>
</xs:group>
</xs:schema>

0 comments on commit b32a33a

Please sign in to comment.