Open dbrianwalton opened 1 month ago
Being overly restrictive/cautious, I think. I would remove the exercise/
and it should (a) behave for task
(and &PROJECT-LIKE
) , and (b) not wreck anything else. I've tested (a), have not done a before/after diff for (b).
If you get a resolution done this afternoon, feel free to just do it. I wouldn't have a chance to actually put together a PR and test until possibly tomorrow based on my current workload.
Made the fix, and put your name on it. ;-) At 4c151d6d2f225fee472c66d387c767d3d267d79c Thanks for being part of the bug-rapid-response team.
Added to the sample article under my name. Comprehensive testing indicates no collateral harm.
The tables that should appear in a static representation for "matching" problems are not generated when in anything other than
exercise
. The relevant templates appear inpretext/xsl/pretext-runestone-static.xsl
:<xsl:template match="exercise/matches/match" mode="matching-statement">
<xsl:template match="exercise/matches/match" mode="matching-solution">
The XPATH match on
exercise
needs to expand to the broader possibilities, probably something likeexercise|&PROJECT-LIKE;|task
, but I'm not sure if that is valid at this level of an XPATH or why it wasn't done initially.