Description
Follow up task after https://phabricator.wikimedia.org/T310666#8332465
Due to a query limitation, the "Longest streak" data only accounts for the last 1,000 edits.
For newcomers and any editor with less than 1,000 edits, that's not a problem. But for any editor with more than 1,000 edits, this means the "longest streak" might not be accurate.
A simple solution could simply be to add a note in the pop-up only for people with >1K edits that the data is based their last 1000 edits?
Proposed copy:
Your current longest streak is 3 days which you achieved between (x) – (y).
The longest streak is the highest number of consecutive days you’ve completed an edit (limited to the last 1,000 edits associated with your account).
Acceptance Criteria
Given I am logged in,
When I have completed 1,000 edits or less,
Then there is no change (I see the current copy when I tap/click on the info icon next to Longest Streak)
Given I am logged in,
When I have completed more than 1,000 edits,
Then I see the Proposed copy instead (when I tap/click on the info icon next to Longest Streak)
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.