Flow maintains its own system of revision storage, which is not implemented in the same manner as that of standard core revisions. Right now, the revision capability of Flow pages, which is inherited from BasePage, is basically useless for practical purposes. This task will use new Flow API calls, view-topic-history and view-post-history, to access Flow content revisions. A new FlowRevision class will be created to represent these revisions.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add Flow-specific revision support | pywikibot/core | master | +446 -77 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T107093 Bots and Flow living in harmony (tracking) | |||
| Invalid | None | T110042 Pywikibot and Flow (tracking) | |||
| Open | None | T109228 Pywikibot and Flow (Phase 2: Moderation and Revision History) (tracking) | |||
| Open | None | T109309 Implement Flow-specific revision history support in Pywikibot | |||
| Resolved | happy5214 | T103032 Expose Flow topic history in API | |||
| Resolved | happy5214 | T103034 Expose Flow post history in API |
Event Timeline
Comment Actions
Change 253385 had a related patch set uploaded (by Happy5214):
[WIP] Add Flow-specific revision support
Comment Actions
@happy5214: Hi! This task has been assigned to you a while ago. Could you maybe share an update? Do you still plan to work on this task? Thanks!
Comment Actions
I thought I had already mentioned it here, but I've been trying to tackle the comments that have been posted on Gerrit.
Comment Actions
I have been waiting for a review on the latest patch changes for two months now. I would greatly appreciate it if this task isn't snatched out from under me due to lack of reviews by the PWB devs.
Comment Actions
Maybe you could split the large patch into some smaller patches to make it easier to review. I think renaming format to content_format is a little bit off-topic to this task.
Comment Actions
This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)