- create architecture to gather the API data and generate what we want
- make API requests based on form fields
- calculate which pages to include
- data is visible just to debug, unformatted
- unit tests
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • TBolliger | T166807 Epic ⚡️ : Interaction Timeline | |||
| Resolved | dbarratt | T178640 Interaction Timeline MVP | |||
| Resolved | dmaza | T178715 Interaction Timeline MVP: Gather edits in chronological order |
Event Timeline
Comment Actions
@dmaza it looks like there are a ton of endpoints that return revisions, but API:Usercontribs at least allows multiple usernames.
Comment Actions
@dmaza Here's an example API query to get all of the pages a user has ever edited:
https://en.wikipedia.org/w/api.php?action=query&generator=allrevisions&callback=&garvuser=Kaldari&garvlimit=500
Comment Actions
@TBolliger This is mostly done.
https://tools.wmflabs.org/interaction-timeline/
The revisions are loaded, but we still need to filter out the revisions to pages that are not edited by both users.
Should we do that as part of this task or create a new one?