Adding UNKNOWN value to Job constraint change enum.

Proto best practices are to have the first value in an enum be similar
to UNKNOWN/UNSET/NONE.

Bug: 120941744
Bug: 120793892
Test: Android builds
Change-Id: I8a764565d14ad6dde93ebfcbd55fd37cf533b253
This commit is contained in:
Kweku Adams
2019-02-27 14:30:34 -08:00
parent 5f9cad60c8
commit e8db3ab5a2

View File

@@ -5528,8 +5528,9 @@ message ScheduledJobConstraintChanged {
optional com.android.server.job.ConstraintEnum constraint = 3;
enum State {
UNSATISFIED = 0;
SATISFIED = 1;
UNKNOWN = 0;
UNSATISFIED = 1;
SATISFIED = 2;
}
optional State state = 4;
}