Move about:welcome code out from browser/components/newtab into its own browser/components directory
Categories
(Firefox :: Messaging System, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox122 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley)
References
(Blocks 3 open bugs, Regressed 2 open bugs)
Details
(Whiteboard: [hnt])
Attachments
(9 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
The code powering the current version of about:welcome has lived under browser/components/newtab since its inception in bug 1616370. It shares some of newtab's infrastructure for things like testing, linting, and building / webpacking / bundling.
We're going to be investing some more in newtab in the coming months, and one thing I'd like to do is try to decouple about:newtab from things like about:welcome so that newtab changes do not adversely affect these other components.
My suggestion is to move the code powering about:welcome into a new directory browser/components/welcome
.
Hey Gijs - I've gotten a thumbs up from pdahiya to attempt this. Any objections if I try to move about:welcome into `browser/components/welcome"?
Assignee | ||
Updated•1 year ago
|
Comment 1•1 year ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) from comment #0)
Hey Gijs - I've gotten a thumbs up from pdahiya to attempt this. Any objections if I try to move about:welcome into `browser/components/welcome"?
No objections, though could we make it aboutWelcome
or similar? :-)
Assignee | ||
Comment 2•1 year ago
|
||
This clones many of the ESLint rules from browser/components/newtab over as well.
Assignee | ||
Comment 3•1 year ago
|
||
Depends on D193116
Assignee | ||
Comment 4•1 year ago
|
||
Depends on D193117
Assignee | ||
Comment 5•1 year ago
|
||
Depends on D193118
Assignee | ||
Comment 6•1 year ago
|
||
Depends on D193119
Assignee | ||
Comment 7•1 year ago
|
||
Depends on D193120
Assignee | ||
Comment 8•1 year ago
|
||
Depends on D193121
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 9•1 year ago
|
||
Depends on D193122
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 10•1 year ago
|
||
This is fairly gross, but basically it uses some directory manipulation to run the
bundling steps and karma tests for both browser/components/newtab and
browser/components/aboutwelcome.
It then also takes the lcov.info files generated by both test runs and
concatenates them together before zipping them up.
Bug 1866170 covers creating a try-runner.js script for
browser/components/aboutwelcome.
Depends on D193228
Updated•1 year ago
|
Comment 11•1 year ago
|
||
Comment 12•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/b06088e7bf14
https://hg.mozilla.org/mozilla-central/rev/2e4ea1016d37
https://hg.mozilla.org/mozilla-central/rev/248515a053d2
https://hg.mozilla.org/mozilla-central/rev/fa9e5979e8f5
https://hg.mozilla.org/mozilla-central/rev/edb7a5027680
https://hg.mozilla.org/mozilla-central/rev/47ce0e918be8
https://hg.mozilla.org/mozilla-central/rev/c72ffc74e4fa
https://hg.mozilla.org/mozilla-central/rev/d5ae6f352563
https://hg.mozilla.org/mozilla-central/rev/b34bd4e8f5e5
Updated•11 months ago
|
Description
•