Find out why mw.wikibase.getEntity (and equivalent) functions are used on the wikis and if replacements exist.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T112073 Lua in Wikibase (tracking) | |||
| Open | None | T189506 Evaluate usages of mw.wikibase.getEntity |
Event Timeline
Comment Actions
No, I'm not actively tackling this… I don't this is overly urgent now, but this might bight us sometime later.
Comment Actions
This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)
Comment Actions
This probably could use some more context. Why do we want to find out how mw.wikibase.getEntity is used? Is this mainly to understand how an expensive function is used in order to maybe optimize that, or is there another motivation?
Comment Actions
I think this was mainly about understanding why more specialized functions are not used and which more specialized functions are missing. The goal was to move people away from the more expensive calls where possible.