Support multi branch, multi token format fills #10
Labels
feature
New feature or request
Comments
LandingEllipse
added a commit
that referenced
this issue
Apr 27, 2021
Treat members of node sets as format token substitutions for fill expressions declared outside of multi branch contexts (where they would otherwise be greedily mapped to branches instead). Fill expressions within multi branches are currently unable to declare more than one substitution (see #10).
LandingEllipse
added a commit
that referenced
this issue
Apr 27, 2021
Treat members of node sets as format token substitutions for fill expressions declared outside of multi branch contexts (where they would otherwise be greedily mapped to branches instead). Fill expressions within multi branches are currently unable to declare more than one substitution (see #10).
LandingEllipse
added a commit
that referenced
this issue
Apr 28, 2021
Ensure pt:sequence unwraps single-member node-sets, and complains in the case of empty of multi-member node-sets (see #10)
LandingEllipse
added a commit
that referenced
this issue
Apr 28, 2021
Ensure pt:sequence unwraps single-member node-sets, and complains in the case of empty of multi-member node-sets (see #10)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've just implemented support for multiple fill format tokens, however fills declared on a multi branch are restricted to yielding a single substitution. The reason being that nested node-sets are not supported in XPath/lxml. For instance, the following raises an
XPathResultError:A way around this could be to use
Elementnesting instead of node-sets for thept:sequenceextension function (i.e. return a detached tree), and change the internal implementation of how fills are handled accordingly (e.g. if we're on a multi branch, select the corresponding child of the evaluated root element, then use its children as token substitutions).The text was updated successfully, but these errors were encountered: