Wikibase does special things (custom html, etc) with what goes into the parser cache. When we deploy new code, we sometimes need to bump $wgCacheEpoch, because of UI changes. We don't bump cache epoch every deploy, so this would make sense as a version constant or such.
I see that Parser has a version constant that is used as part of determining expiry in CacheTime.
It would be great if a Wikibase "Parser" version could also be used in determining cache expiry.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add version constant for EntityContent for parser options | mediawiki/extensions/Wikibase | master | +30 -24 |
Change 188277 had a related patch set uploaded (by Aude):
Add version constant for EntityContent for parser options
PageRenderingHash doesn't know anything about content model / type.
looks like the best way is ParserOptions::addExtraKey, which can be used for EntityContent while for non-entity content, we don't need to interfere. We can have a version constant for EntityContent that we bump when we have breaking changes.
then when we deploy, the version change / cache bump goes out same time as the code changes vs. trying to handle this in a wmf config setting.
Change 188277 merged by jenkins-bot:
Add version constant for EntityContent for parser options
Patch approved... now we "only" need to remember to bump that constant whenever we do breaking changes.