Version: unspecified
Severity: enhancement
Description
Description
Details
Details
- Reference
- bz72705
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T49145 Formally deprecate jQuery UI after we've stopped using jQuery UI in extensions and core | |||
| Open | None | T100270 Replace use of jQuery UI and MW UI with OOUI across all Wikimedia-deployed extensions and core | |||
| Resolved | • matmarex | T74715 Convert some MW core special pages to OOUI | |||
| Resolved | • TrevorParscal | T74714 Provide the OOUI PHP module inside MW core | |||
| Resolved | • TrevorParscal | T74713 Get OOUI PHP to be good to go | |||
| Resolved | • matmarex | T74705 OOUI PHP: Use a namespace for our classes |
Event Timeline
Comment Actions
gerritadmin wrote:
Change 170501 had a related patch set uploaded by Bartosz Dziewoński:
OOUI PHP: Use 'OOUI' namespace instead of 'OoUi' class name prefix
Comment Actions
gerritadmin wrote:
Change 170501 merged by jenkins-bot:
OOUI PHP: Use 'OOUI' namespace instead of 'OoUi' class name prefix
Comment Actions
There were some concerns raised on the patch that this usage doesn't quite match PHP best practices, but we'd need to do quite a bit of renaming to do that (also on the JS side to stay consistent).
I'm open to suggestions that don't require me to do massive semi-manual search-and-replaces on thousands of lines of code that uses JS OOUI already. :)