diff options
| author | 2023-11-09 13:11:02 -0800 | |
|---|---|---|
| committer | 2023-11-09 16:05:58 -0800 | |
| commit | e60d5c87954bb10c3f6a6013f07a0878ed72f5a7 (patch) | |
| tree | f9eb8022f7024cc54f3b0dea7499a8eea9508612 /api/api.go | |
| parent | 7a338c16efe7ff36444d706b264b1cb1116bcf63 (diff) | |
Remove released flag SMARTSPACE_DATE_WEATHER_DECOUPLED and its use sites.
Also, fixed a mistake in LSController.filterSmartspaceTarget. After the
flag value in LSControllerTest, the mistake was caught by the following
unit tests:
- testSettingsAreReloaded
- testSensitiveTargetsAreFilteredOutForAppropriateUsers
- testRecognizeSwitchToSecondaryUser
- testAllTargetsAreFilteredExceptWeatherWhenNotificationsAreDisabled
I believe the mistake caused a regression on filtering sensitive targets
for work profile. See http://b/277963509#comment14 for more details.
Flag: LEGACY SMARTSPACE_DATE_WEATHER_DECOUPLED NEXTFOOD
Bug: 309825884
Bug: 277963509
Test: unit (see updated Test files)
Test: on device, trigger alarm, dnd, timer, calendar
Change-Id: I33075849ca95c1bab5f9260eaf7506513883efef
Diffstat (limited to 'api/api.go')
0 files changed, 0 insertions, 0 deletions