Open
Bug 2023759
Opened 2 months ago
Updated 2 months ago
Find a better abstraction location for NimbusGeckoPrefHandler
Categories
(Firefox for Android :: Experimentation and Telemetry, task)
Tracking
()
NEW
People
(Reporter: olivia, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxdroid][group6])
NimbusGeckoPrefHandler should be in a better abstraction to get more business logic outside of the app layer.
Some current thoughts are to upstream NimbusGeckoPrefHandlert to service-nimbus or a new one that connectgs concept-engine and service-nimbus together. See :jonalmeida's comments on D284590 for more context.
| Reporter | ||
Updated•2 months ago
|
Whiteboard: [fxdroid][group6]
Updated•2 months ago
|
| Reporter | ||
Comment 1•2 months ago
|
||
Might make sense to layer out the files into:
- enrollment flow
- unenrollment flow
- observation flow
These distinct flows are all grouped together in NimbusGeckoPrefHandler and it makes deconstructing the behavior difficult.
You need to log in
before you can comment on or make changes to this bug.
Description
•