After T401288 is implemented, it might worth to investigate existing modules.
We want to maximise the effect of granular entity usage tracking by making sure modules are written in compliance with it. As it is mentioned in this comment written after X usage is implemented, we see module code could make a difference.
Similar to T381098 and can be merged for research.
E.g. look at modules in the wiki clients
Checklist:
- Is it a common practice to access an entity aspect with a specific language? Or do they access all and iterate through them with a for loop to find the one they need?
- Locally: if we access the whole object or whole entity aspect, do we get entity usage about the other usages as well (is it acting like a bundle when we read the whole object)
- Is there a way for seeing which module affects which pages & vice versa?
- Consider EU and RC are stored on different tables
- Calculate baselines if possible to compare later
- Is X usage really needed on RC table (since it dos not include aliases now). To find out: is it possible to be subscribed to X usage currently? How common is that? (maybe this needs to go to another ticket)
- Is X usage still in the tables anyways? Verification needed.
Acceptance criteria:
- possible follow up tickets