diff options
| author | 2023-10-06 11:01:32 -0700 | |
|---|---|---|
| committer | 2023-10-06 13:34:28 -0700 | |
| commit | 6fa7a3c7c5213ad3a94406f46fec6d1219b3fa43 (patch) | |
| tree | 7aa3ee8de30ae35a4e9927e9e767e674a197aaeb /api/api_test.go | |
| parent | c7f2ff98f315caa5b738bd94aa067d66af4c726c (diff) | |
[aapt2] Generate @FlaggedApi annotations
Like we currently do for @TestApi and @SystemApi, we look for
"@FlaggedApi" and its parameters in the comment above the resource.
Bug: 295328308
Test: Did the following:
1. Ran `atest aapt2_tests`
2. Ran `aapt2 link` on public-staging.xml with an added @FlaggedApi
in the comment for the resource currently there. Verified the
@FlaggedApi annotation is present in the generated R.java.
3. Ran `m framework-minus-apex` and it built successfully.
4. Modified the @FlaggedApi comment with an invalid value (e.g.,
`Flags.FOO` which does not exist). The build failed. Since
@FlaggedApi is a source-only annotation (i.e., not present in the
R.class file), we want to verify it was actually used in the build.
Change-Id: I0739f888d40269915c0acea5650c386da1a1782e
Diffstat (limited to 'api/api_test.go')
0 files changed, 0 insertions, 0 deletions