Index Data to build Slices in Settings
The indexing is done by taking the indexable fragments from search, grabbing their XML via SearchIndexableResources, and then looking for controllers defined in preferences. For each controller found, we take the combination of the fragment providing the XML and the Preference info to create an indexable row. Buiding a Slice will be handled in a subsquent CL, but a prototype can be found here: ag/3324435 Test: robotests Bug: 67996923 Change-Id: I48668618079bcc3da55ab77b7323ee8e467073af
This commit is contained in:
@@ -20,8 +20,7 @@ import android.net.Uri;
|
||||
import android.text.TextUtils;
|
||||
|
||||
/**
|
||||
* TODO (b/67996923) Add SlicesIndexingManager
|
||||
* Data class representing a slice stored by {@link SlicesIndexingManager}.
|
||||
* Data class representing a slice stored by {@link SlicesIndexer}.
|
||||
* Note that {@link #key} is treated as a primary key for this class and determines equality.
|
||||
*/
|
||||
public class SliceData {
|
||||
@@ -173,10 +172,6 @@ public class SliceData {
|
||||
throw new IllegalStateException("Preference Controller cannot be empty");
|
||||
}
|
||||
|
||||
if (mUri == null) {
|
||||
throw new IllegalStateException("Uri cannot be null");
|
||||
}
|
||||
|
||||
return new SliceData(this);
|
||||
}
|
||||
|
||||
|
Reference in New Issue
Block a user