Call SystemUIFactory.prepareSysUIComponentBuilder even for tests
Thus any downstream project can customize SysUIComponent.Builder for their tests. Bug: 171436765 Test: atest SystemUITests Change-Id: I033dd144b21b99b8f455775099f7ecb6a1dffe6b
This commit is contained in:
@@ -113,8 +113,10 @@ public class SystemUIFactory {
|
||||
.setShellCommandHandler(mWMComponent.getShellCommandHandler())
|
||||
.setAppPairs(mWMComponent.getAppPairs());
|
||||
} else {
|
||||
// TODO: Call on prepareSysUIComponentBuilder but not with real components.
|
||||
builder = builder.setPip(Optional.ofNullable(null))
|
||||
// TODO: Call on prepareSysUIComponentBuilder but not with real components. Other option
|
||||
// is separating this logic into newly creating SystemUITestsFactory.
|
||||
builder = prepareSysUIComponentBuilder(builder, mWMComponent)
|
||||
.setPip(Optional.ofNullable(null))
|
||||
.setSplitScreen(Optional.ofNullable(null))
|
||||
.setOneHanded(Optional.ofNullable(null))
|
||||
.setBubbles(Optional.ofNullable(null))
|
||||
@@ -194,4 +196,4 @@ public class SystemUIFactory {
|
||||
AssetManager am, String modelName) {
|
||||
return new BackGestureTfClassifierProvider();
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user