Last modified: 2010-02-04 23:41:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 20354 - Use LiquidThreads to implement comments for CodeReview
Use LiquidThreads to implement comments for CodeReview
Status: RESOLVED DUPLICATE of bug 20542
Product: MediaWiki extensions
Classification: Unclassified
CodeReview (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Andrew Garrett
Depends on:
Blocks: 18378
  Show dependency treegraph
Reported: 2009-08-22 17:49 UTC by Brion Vibber
Modified: 2010-02-04 23:41 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Brion Vibber 2009-08-22 17:49:34 UTC
Currently the CodeReview extension implements a custom threaded commenting system. As LiquidThreads continues to mature and stabilize, it would be great to use it to handle the comments so we have a common user interface, storage, etc; it'll keep things consistent and simpler... in theory at least. ;)

This'll need work on the LQT end to support embedding in the other extension's form and some hooks to handle the extra transformations for auto linking of revision and bug numbers.

On the CodeReview end, a conversion from the old comment storage will be needed, as well as making sure we've still got proper integration of the comment counts and notifications.
Comment 1 Andrew Garrett 2010-02-04 23:41:20 UTC

*** This bug has been marked as a duplicate of bug 20542 ***

Note You need to log in before you can comment on or make changes to this bug.