Open
Bug 2002483
Opened 7 months ago
Updated 3 months ago
Refactor DefaultDeleteBrowsingDataController into an use case.
Categories
(Firefox for Android :: Tooling, task)
Tracking
()
NEW
People
(Reporter: mcarare, Unassigned)
References
Details
(Whiteboard: [fxdroid][group6])
From the initial refactoring review:
jonalmeida: Your new stateless controller that you've built looks a lot like a higher-level use case itself. This is good because I always think of them as interchangeable in my head.
I think you could simplify it's usage in all those fragments, but building a single instance of it in one place (our homegrown dep tree Components.kt), or make a simple type of builder so you don't have to do that on every fragment. WDYT?
If you decide to go with the former, then I'd suggest the consistent naming of "UseCase".
|
||
Updated•7 months ago
|
|
||
Comment 1•7 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox for Android::Tooling' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Component: General → Tooling
|
Reporter | |
Updated•3 months ago
|
Assignee: mcarare → nobody
Status: ASSIGNED → NEW
You need to log in
before you can comment on or make changes to this bug.
Description
•