|
Ran
|
Files
86
|
Run time
5s
|
Badge
README BADGES
|
push
travis-ci
<a href="https://github.com/wikimedia/parsoid/commit/b5970c4d7">Restrict nested refs not coming from templates This better matches the behaviour of the php extension. An instructive example is, <ref>123 {{#tag:ref|321}}</ref> {{#tag:ref|456 <ref>654</ref>}} The php implementation only parses the ref contents when producing the output for reference tags, at which point, nested refs will be ignored, as in the former case. The "321" is dropped. The latter is special, since the extension tag takes precedence over the parser function, the inner ref will already have been processed when the outer is added to the stack, and hence the nesting is permitted. This is why the inner ref precedes the outer in the references list (has a lower number). Unfortunately, Parsoid doesn't yet get that ordering right. Change-Id: I</a><a class="double-link" href="https://github.com/wikimedia/parsoid/commit/eb0e418cc">eb0e418cc</a>
8927 of 10965 branches covered (81.41%)
14446 of 16786 relevant lines covered (86.06%)
24648.7 hits per line
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|