Page MenuHomePhabricator

Stop using webpack in mobile.editor.overlay module
Open, Needs TriagePublic

Description

Background

The web team would like to move away from webpack in MobileFrontend to avoid having to do a costly upgrade with little benefit. We plan to do this gradually on a per-feature basis to avoid any breakages.

Before doing this we would need buy-in from the editing team who co-maintain the MobileFrontend repository.

User story

As a developer I want to remove unhelpful dependencies from my codebases.

Requirements

  • The mobile.editor.overlay module no longer requires webpack to be built
  • The editing team is happy with this interim state

BDD

  • For QA engineer to fill out

Test Steps

  • For QA engineer to fill out

Design

  • Add mockups and design requirements

Acceptance criteria

  • Add acceptance criteria

Communication criteria - does this need an announcement or discussion?

  • Add communication criteria

Rollback plan

  • What is the rollback plan in production for this task if something goes wrong?

This task was created by Version 1.2.0 of the Web team task template using phabulous

Event Timeline

Editing engineers would be happy with this. Going module by module will be a little confusing for a while but hopefully that won't be too long, and the end state will be a great improvement.

Side note: you may want to trim the subscribers list when creating a sub task :)

Change #1091375 had a related patch set uploaded (by Jdlrobson; author: Jdlrobson):

[mediawiki/extensions/MobileFrontend@master] Move mobile.editor.overlay off of Webpack

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

No urgency @Esanders but there's the MVP for what that would look like for editing engineers to look at whenever time allows.

LGTM - happy to merge when you guys are ready.

LGTM - happy to merge when you guys are ready.

My hope was that editing team could merge and QA this since you are more familiar with the codebase and I see you as maintainers of that code and would get the most benefits. With that in mind you can merge whenever makes sense!

In terms of the rest of the codebase, I'm hoping we can begin the transition away from Webpack next quarter (possibly starting earlier in December if we make more progress than expected on the other things we have in flight).

Esanders moved this task from Incoming to QA on the Editing-team (Kanban Board) board.

For editing QA, we should check that the basic workflows of mobile editing are unaffected:

  • open the editor
  • switch edit modes (visual/source)
  • close the editor
  • publish changes (both modes)

Change #1091375 merged by Jdlrobson:

[mediawiki/extensions/MobileFrontend@master] Move mobile.editor.overlay off of Webpack

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

Change #1094065 had a related patch set uploaded (by Jdlrobson; author: Jdlrobson):

[mediawiki/extensions/MobileFrontend@master] Fixes: switching between VisualEditor and SourceEditor

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

Change #1094065 merged by jenkins-bot:

[mediawiki/extensions/MobileFrontend@master] Fixes: switching between VisualEditor and SourceEditor

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