Fixed
Status Update
No update yet.
Comments
da...@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.
da...@google.com
ap...@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.
Description
Currently for queries like `SELCT *` we can use return type List<Model>. Can we also support ArrayMap<String, Model> (for TEXT type primary key) or ArrayMap<Long, Model> (for INTEGER type primary key). This will make traversing faster in this list of elements.
I haven't tried HashMap but support, that would also be great.
SparseArray in case of INTEGER type primary key can also make sense.