Intermediate counts have been hardcoded for user testing. We need to implement it with live data when the endpoint is ready.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | LGoto | T216665 As a curating editor I want to be able to see a useable page history and take revert actions | |||
| Resolved | • JMinor | T228792 Compare revision: as a user I want to compare two revisions in my history | |||
| Resolved | • JMinor | T238219 Diff Compare - implement intermediate counts endpoint when ready |
Event Timeline
Comment Actions
Per Evan these endpoints should work:
Editor count:
https://en.wikipedia.org/w/rest.php/v1/page/Dog/history/counts/editors?from=918180393&to=925652284
Edit count:
https://en.wikipedia.org/w/rest.php/v1/page/Dog/history/counts/edits?from=918180393&to=925652284
It does look like it has limits so maybe we'll want to display something like "1000+ edits by 1000+ editors not shown" if the limit is reached?
Comment Actions
@Tsevener yeah, I think as long as the cap is higher than most articles, this should work (eg. 500 just felt much too low)
And I would say that ideally, having the exact number for number of edits is probably slightly more necessary than raw number of editors.