Fixed
Status Update
Comments
je...@google.com <je...@google.com> #2
This was fixed by aosp/1331903 and will be available in the Lifecycle 2.3.0-alpha04 release.
sh...@google.com <sh...@google.com> #3
Project: platform/frameworks/support
Branch: androidx-master-dev
commit f891d66d44417ae7298d8306dc5cbca9cfe4b1ee
Author: Jeremy Woods <jbwoods@google.com>
Date: Wed Jul 08 14:20:29 2020
Fix lifecycle-livedata-core-ktx-lint ObsoleteLintCustomCheck
Using the latest version of lint-core (27.1.0) as a dependency for the
livedata-core lint rule causes an ObsoleteLintCustomCheck for studio 4.0
and 4.1 (along with the subsequent gradle versions).
Instead of using the latest, using the minimum version seems to work
appropriately.
Added a lintMinVersion variable to the dependcies file and used that to
make updating easier.
Test: tested in studio 4.0 and 4.1-Canary 8
Bug: 158699265
Change-Id: If1636b3e08a368cf25fb268f42754c4c6ff2f463
M buildSrc/src/main/kotlin/androidx/build/dependencies/Dependencies.kt
M lifecycle/lifecycle-livedata-core-ktx-lint/build.gradle
https://android-review.googlesource.com/1358530
Branch: androidx-master-dev
commit f891d66d44417ae7298d8306dc5cbca9cfe4b1ee
Author: Jeremy Woods <jbwoods@google.com>
Date: Wed Jul 08 14:20:29 2020
Fix lifecycle-livedata-core-ktx-lint ObsoleteLintCustomCheck
Using the latest version of lint-core (27.1.0) as a dependency for the
livedata-core lint rule causes an ObsoleteLintCustomCheck for studio 4.0
and 4.1 (along with the subsequent gradle versions).
Instead of using the latest, using the minimum version seems to work
appropriately.
Added a lintMinVersion variable to the dependcies file and used that to
make updating easier.
Test: tested in studio 4.0 and 4.1-Canary 8
Bug: 158699265
Change-Id: If1636b3e08a368cf25fb268f42754c4c6ff2f463
M buildSrc/src/main/kotlin/androidx/build/dependencies/Dependencies.kt
M lifecycle/lifecycle-livedata-core-ktx-lint/build.gradle
je...@google.com <je...@google.com> #4
There was a use of a lint version that was too new to work in older studio versions. This has now be fixed and will be released in the Lifecycle 2.3.0-alpha06 release.
je...@google.com <je...@google.com>
ap...@google.com <ap...@google.com> #5
Getting this again in AGP 8.2.2 and Gradle 8.6, please see the attached image file.
je...@google.com <je...@google.com> #6
Just found out that the issue comes after updating androidx.lifecycle:lifecycle-livedata-ktx
from 2.7.0 to 2.8.0.
ap...@google.com <ap...@google.com> #7
Using AGP 8.5.1 with Gradle 8.7 makes the latest occurrence of this go away for me (with androidx.lifecycle:lifecycle-runtime-ktx
2.8.4).
Description
The reasoning is that the padding defines the content rectangle, and whether or not children's pixels are clipped to that rectangle or not doesn't change the semantics of that rectangle.
Consider for example a horizontal ViewPager2 that has unequal padding on the left and the right. When it is in idle state, a page exactly fills the rectangle described by the inner edge of the padding, so the page looks to be off-center by design. When snapping kicks in (e.g., because of a swipe), the page to which it is snapping should end up in that same "off-center" position, exactly matching the rectangle described by the inner edge of the padding, regardless of the value of clipToPadding.