Remove the direct dependency of appservices search from the fenix/app/build.gradle
Categories
(Firefox for Android :: Search, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox138 | --- | unaffected |
firefox139 | --- | wontfix |
firefox140 | --- | fixed |
People
(Reporter: jonalmeida, Assigned: harrisono)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fxdroid][group3][search-consolidation])
Attachments
(1 file)
With bug 1944964, our feature-search component and fenix now depending on our app services component. We should avoid leaking our dependencies through the abstractions and making the our module component and the app have the same dependency because this leads us closer to having circular dependencies or lead to application code interacting with the dependency directly and cause a broken state.
In this particular case, the dependency is mostly needed for enums or , so a possible solution could be to map one enum to an AC enum - which is probably a bit heavy, but we do have fairly good examples of this:
Comment 1•2 months ago
|
||
Set release status flags based on info from the regressing bug 1944964
:harrisono, since you are the author of the regressor, bug 1944964, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Updated•2 months ago
|
Updated•2 months ago
|
Assignee | ||
Comment 2•2 months ago
|
||
Updated•2 months ago
|
Updated•2 months ago
|
Comment 4•2 months ago
|
||
bugherder |
Comment 5•2 months ago
|
||
The patch landed in nightly and beta is affected.
:harrisono, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox139
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 6•2 months ago
|
||
Change is not important enough to warrant an uplift to beta for 139.
marking 139 as "wontfix"
Description
•