Use CustomSliceRegistry directly when possible.

This is one step closer to (un)make CustomSliceManager an singleton.

Bug: 123937830
Test: manual
Change-Id: I844d0fb798c73e2af1945ecb667ba73fac9edf72
This commit is contained in:
Fan Zhang
2019-03-13 15:58:18 -07:00
parent 6120d57cbc
commit ad29500d1d
6 changed files with 12 additions and 44 deletions

View File

@@ -57,15 +57,4 @@ public class CustomSliceManager {
mSliceableCache.put(newUri, sliceable);
return sliceable;
}
/**
* Return a {@link CustomSliceable} associated to the Action.
* <p>
* Do not change this method signature to accommodate for a special-case sliceable - a context
* is the only thing that should be needed to create the object.
*/
public CustomSliceable getSliceableFromIntentAction(String action) {
return getSliceableFromUri(Uri.parse(action));
}
}