https://bugzilla.wikimedia.org/show_bug.cgi?id=59788
--- Comment #7 from Brad Jorsch <bjor...@wikimedia.org> --- (In reply to comment #6) > Using prepareContentForEdit() just to get a cached version of the parser > output > seems evil... not to mention that prepareContentForEdit() is pretty bad of > and > by itself and should be avoided. Why is that, exactly? See bug 57026, BTW. It seems to me that calling prepareContentForEdit() in an editing hook makes complete sense. > * use the ParserOutputCache directly "ParserOutputCache" doesn't exist. ParserCache works on the current version of an article, which isn't going to help much when you don't have an article yet and you haven't yet saved the text. > * make getParserOutput cache the last result it returned, and return it again > if the parameters are the same. That doesn't help when not everything uses the same Content object. Or a Content object at all. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
