From 0dd6333b087c5d46e9815dd55b3a6777bd5a4f73 Mon Sep 17 00:00:00 2001 From: Hai Zhang Date: Tue, 25 Oct 2022 20:24:54 +0000 Subject: [PATCH] Clarify that OPSTR constants don't have to be system APIs. System APIs should only be created when needed. Test: presubmit Change-Id: I9e00b7a3008e71ce2a7ebaeac31c545137606477 --- core/java/android/app/AppOpsManager.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/java/android/app/AppOpsManager.java b/core/java/android/app/AppOpsManager.java index 3f39026c81896..d1275f66383e8 100644 --- a/core/java/android/app/AppOpsManager.java +++ b/core/java/android/app/AppOpsManager.java @@ -867,7 +867,7 @@ public class AppOpsManager { // when adding one of these: // - increment _NUM_OP - // - define an OPSTR_* constant (marked as @SystemApi) + // - define an OPSTR_* constant (and mark as @SystemApi if needed) // - add row to sAppOpInfos // - add descriptive strings to Settings/res/values/arrays.xml // - add the op to the appropriate template in AppOpsState.OpsTemplate (settings app)