Turns off use of refactord UserSwitcherController.
There was an automatically detected massive regression in performance, as seen in the attached bug. This flag change shuts down the use of UserInteractor instead of the controller. Now, we have time to locally investigate the performance regression before turning that on again. Fix: 253435919 Test: verified that user switcher is still working Change-Id: I716439dcbe55e998687229ab0e68176548eff685
This commit is contained in:
@@ -111,8 +111,8 @@ public class Flags {
|
||||
* <p>If this is {@code false}, the interactor and repo skip the controller and directly access
|
||||
* the framework APIs.
|
||||
*/
|
||||
public static final UnreleasedFlag USER_INTERACTOR_AND_REPO_USE_CONTROLLER =
|
||||
new UnreleasedFlag(210);
|
||||
public static final ReleasedFlag USER_INTERACTOR_AND_REPO_USE_CONTROLLER =
|
||||
new ReleasedFlag(210);
|
||||
|
||||
/**
|
||||
* Whether `UserSwitcherController` should use the user interactor.
|
||||
@@ -123,7 +123,7 @@ public class Flags {
|
||||
* <p>Note: do not set this to true if {@link #USER_INTERACTOR_AND_REPO_USE_CONTROLLER} is
|
||||
* {@code true} as it would created a cycle between controller -> interactor -> controller.
|
||||
*/
|
||||
public static final ReleasedFlag USER_CONTROLLER_USES_INTERACTOR = new ReleasedFlag(211);
|
||||
public static final UnreleasedFlag USER_CONTROLLER_USES_INTERACTOR = new UnreleasedFlag(211);
|
||||
|
||||
/***************************************/
|
||||
// 300 - power menu
|
||||
|
||||
Reference in New Issue
Block a user