Felipe Leme bb6bfea680 Refactored the FieldsClassification score mechanism. ...

Before, FillEvent.getFieldsClassification() returned a map of remote ids and
scores. Now, it returns a Map of FieldClassication by AutofillId, which allows
multiple fields and scores for multiple user datas (although the initial
implementation supports only the top match for a field).

This is mostly a refactoring CL, as the implementation is still saving just one
user data entry and one field. But full support is coming next...

Test: atest CtsAutoFillServiceTestCases:FieldsClassificationTest
Test: atest CtsAutoFillServiceTestCases:UserDataTest
Test: atest CtsAutoFillServiceTestCases:FieldsClassificationScorerTest

Bug: 68045531

Change-Id: I08b29f24efbd527216f9bce2343e1bcd4b4554c0

2017-12-06 11:20:10 -08:00

..

current.txt

Merge "Introduce more user management APIs"

2017-12-06 19:10:34 +00:00

removed.txt

Deeper sanity checking of emitted types.

2017-11-27 17:07:40 -07:00

system-current.txt

Merge "Adds metadata to InstantAppResolveInfo"

2017-12-06 18:05:32 +00:00

system-removed.txt

Deeper sanity checking of emitted types.

2017-11-27 17:07:40 -07:00

test-current.txt

Refactored the FieldsClassification score mechanism.

2017-12-06 11:20:10 -08:00

test-removed.txt

Emit all APIs using Predicates.

2017-11-22 12:34:08 -07:00