Page MenuHomePhabricator

Implement Flow-specific revision history support in Pywikibot
Open, MediumPublic

Description

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.

Event Timeline

happy5214 claimed this task.
happy5214 raised the priority of this task from to Medium.
happy5214 updated the task description. (Show Details)
happy5214 added a project: Pywikibot-Flow.
happy5214 moved this task from Other Pywikibot to Phase 2 on the Pywikibot-Flow board.
Qgil removed a subscriber: Qgil.Oct 12 2015, 3:37 PM
Mpaa added a subscriber: Mpaa.Oct 12 2015, 5:42 PM

Change 253385 had a related patch set uploaded (by Happy5214):
[WIP] Add Flow-specific revision support

https://gerrit.wikimedia.org/r/253385

Huji moved this task from Backlog to Needs Review on the Pywikibot board.Sep 10 2019, 11:29 AM

@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!

I thought I had already mentioned it here, but I've been trying to tackle the comments that have been posted on Gerrit.

happy5214 added a comment.EditedMay 20 2020, 8:01 PM

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.

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.

Aklapper removed happy5214 as the assignee of this task.Fri, Jun 19, 4:24 PM

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!)