Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
What should we do about subpipelines that end with a variable? #693
<p:group> <p:identity/> <p:variable name="irrelevant" select="count(//*)"/> </p:group>
Variables aren't steps, so the last step of this subpipeline is
This is fine, I suppose. The output of the identity step will be consumed by both the group and the variable. That's not a problem, per se. It looks a little weird though.
We could forbid this, but that would require adding (a little more) complexity to the spec. And it's not something anyone is likely to do.
I propose that we add this to the test suite so that we can be sure processors do the right thing but otherwise ignore it.
Thoughts or objections?