diff options
| author | 2024-10-24 10:02:02 +0100 | |
|---|---|---|
| committer | 2024-10-24 10:55:24 +0100 | |
| commit | 3ffd1b2958d6fee2627091b3a4e054aeca07178d (patch) | |
| tree | 9e45edd4b0b35fd71960367e5eb2564a42f928c1 /api/api_test.go | |
| parent | 9b469e030da164dcba298d6e7091f7846712a542 (diff) | |
Remove flag dependency of `status_bar_connected_displays`
`status_bar_connected_displays` was depending on
`status_bar_simple_fragment`. Since both are fairly independent, and
have different timelines, it is best to remove the dependency.
Changes:
- StatusBarOrchestrator related changes are now behind
`status_bar_connected_displays` instead of
`status_bar_simple_fragment`.
- Dagger changes:
- StatusBarInitializer is CoreStartable iff
`status_bar_simple_fragment` is enabled
- StatusBarOrchestrator is never CoreStartable. It will always be
started via MultiDisplayStatusBarStarter.
Test: CentralSurfacesImplTest.java
Test: StatusBarInitializerTest.kt
Test: StatusBarOrchestratorTest.kt
Test: Manually - Build and run with both flags enabled, disabled, and
enabled independently.
Flag: com.android.systemui.status_bar_connected_displays
Bug: 362720336
Change-Id: I2f464b39353b1db9e5f8d01991b5f0b75a37c654
Diffstat (limited to 'api/api_test.go')
0 files changed, 0 insertions, 0 deletions