In T124356#1954680, @tstarling pointed out that 969561ae3c9051eb408626e9b6debb6c0f210b71 broke the semantics of ParserOutput::getText(). This ticket proposes that we fix that breakage.
All users, by default, should receive unprocessed text without skin-specific section edit links and TOC. Any callsite that needs the fully expanded text should explicitly request it with the new method to be introduced (getExpandedText, or whatever it is).
This can prevent newer instances of T124356.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | None | T127757 ParserOutput: Fix semantics of getText() to return text; Introduce getExpandedText (bikeshed name in comments) to return processed text with edit links + toc, etc. | |||
| Resolved | ssastry | T120345 Set up mass visual diff testing with a custom install of mediawiki | |||
| Resolved | bd808 | T125882 Create labs project for parsing team to run experimental mediawiki installs |
@tstarling seems on board with call-sites explicitly opt-ing into getting fully processed output. However, he had more specific ideas about how this processing would be done that goes beyond the interface stub in the title of the ticket. I'll let him document the specifics here.
This is probably a dup of T293512: ParserOutput::getText() should be removed from ParserOutput now.