Closed MichielCM closed 5 years ago
Hello Michiel, great work with this project, thank you!
I think that this issue isn't completely closed because I'm having some troubles with the
Kind regards, Luca.
Thanks for the notification. I should never commit without testing... :)
It looks like I forgot to include the $choice variable in the xs:sequence file. In matchers/sequence.xsl, add a parameter to the template:
And pass it in the apply-templates call in the same template:
Does that fix the issue?
Thanks! This in partially fixes the issue but now even every element in the sequence contained in the choice has it's own checkbox.
<xs:choice>
<xs:sequence>
<xs:element name="CustomerID" />
</xs:sequence>
<xs:sequence>
<xs:element name="Name" />
<xs:element name="Surname" />
</xs:sequence>
</xs:choice>
With this code, for example, the generated html form has a checkbox for CustomerID
, Name
and Surname
instead of having only two checkboxes: one that enables CustomerID
and the other one that enables both Name
and Surname
fields.
I had to refactor quite a bit of code for this to be fixed, but it should work now. Can you check the latest commit and confirm?
During my humble tests all went fine after your latest commit, thank you!
Great, you're welcome! :)
Fixed in release 3.1.