Fixed
Status Update
No update yet.
Comments
al...@google.com
Thank you for submitting the feedback. But we are unable to reproduce the issue on 3.3 RC1 from our end. If you can provide a sample project or a screenshot of the issue it will be really helpful to triage the issue.
If we do not get an update in the next 30 days we will close this issue.
If we do not get an update in the next 30 days we will close this issue.
al...@google.com
al...@google.com
Hi,
Here's a sample project that can reproduce the issue by running Lint : ./gradlew lint
The lint result file is present at the root of the project.
It reproduces the wrong InlinedApi warning & NewApi error.
I've also updated the project to use the new 3.3-rc2 version.
In fact, it's only reproductible when a project have multiple modules.
In my sample there is a class `AndroidVersions` that is in a `core` module and which is used in my `app` module (in MainActivity class).
If the 2 classes are in the same modules, Lint is running properly. But moving the `AndroidVersions` to the core module break it.
Here's a sample project that can reproduce the issue by running Lint : ./gradlew lint
The lint result file is present at the root of the project.
It reproduces the wrong InlinedApi warning & NewApi error.
I've also updated the project to use the new 3.3-rc2 version.
In fact, it's only reproductible when a project have multiple modules.
In my sample there is a class `AndroidVersions` that is in a `core` module and which is used in my `app` module (in MainActivity class).
If the 2 classes are in the same modules, Lint is running properly. But moving the `AndroidVersions` to the core module break it.
ap...@google.com
Hi, the issue is still reproducible with the 3.3-rc03 version.
lo...@gmail.com
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
Description
Library used: AndroidX Annotations
Version used: 1.2.0-beta01
Hello!
It'd be very helpful to have the
@RestricToannotation fromandroidx.annotationbe@Documentedso we see it right into the IDE.It's especially important for CameraX users as there's many restricted symbols appearing in auto-completion, on its only when we try to use them that we see the error, and there's no way to see it's restricted from the quick documentation popup.
Adding the
@Documentedannotation will help to spot them.Thank you for considering, have a great day!
Louis CAD