The user impact API (T313330) allows querying impact data for arbitrary users.
For convenience in debugging and understanding display issues, we should enable a mechanism to allow us to see the new impact module (T222310) with data for any user.
Two ways we could do that:
- Reuse the existing Special:Impact page to load the new impact module, and allow passing the username as a parameter, e.g. Special:Impact/KHarlan_(WMF).
- Pass a query parameter to Special:Homepage, something like Special:Homepage?geImpactModuleUsername=KHarlan_(WMF), where on page load the impact module would load data for KHarlan_(WMF) rather than the current logged-in user.
The first option seems less confusing to me, but open to the second idea too.
I think we should also think about a design variation so that it's obvious that the impact module is showing data for a user other than yourself.
Acceptance Criteria
- Should be able to debug the new impact module appearance for arbitrary accounts
- ....
Completion checklist
Functionality
- The patches have been code reviewed and merged
- The task passes its acceptance criteria
Engineering
- There are existing and passing unit/integration tests
- Tests for every involved patch should pass
- Coverage for every involved project should have improved or stayed the same
Design & QA
- If the task is UX/Design related: it must be reviewed and approved by the UX/Design team
- Must be reviewed and approved by Quality Assurance.
Documentation
- Related and updated documentation done where necessary
- Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc)
- Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on Extension:GrowthExperiments or Extension:GrowthExperiments/Technical documentation pages.