IssueTracker

> The Transition Kotlin extensions target the Framework Transition class which is a bit confusing

All extensions in 'core-ktx' target either 'core' or the framework types. This is working as expected. It sounds like this is a feature request for a transition-ktx with equivalent extensions for the androidx.transition types.

> as most framework classes are being deprecated in favor of their AndroidX counterparts, Fragments for example.

"Most"? This *dramatically* overstates what is actually happening. Fragments (and loaders) were added to the framework in a time where the Android team did not have external libraries for shipping features. Transition was added 5 years later.

Pardon my misunderstanding, I was under the belief that where possible, new features that could be developed outside the framework, would be under Androidx. Also it's a common refrain to use the Androidx libraries over the framework libraries where possible, as those ship update independently of platform releases. I wasn't attempting to be dramatic.

If the Transition api is unlikely to change, there is no need for a transition-ktx for androidx.transition types. If developers should use Androidx transitions over framework transitions where possible however, then it would be much appreciated.

I am well aware of the limitations that existed when Fragments and Loaders were created, and when the Transition api was introduced.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit ae42e311ecfbac18cedc90e489d1fdde956a4557
Author: Jake Wharton <jakew@google.com>
Date:   Fri Nov 22 11:13:30 2019

    Introduce transition-ktx for standalone transition library
   
    These extensions are the same as androidx.core.transition for the platform types, just adapted to the standalone library.
   
    Bug: 138870873
    Test: gw :transition:transition-ktx:build :transition:transition-ktx:connectedCheck
    Change-Id: Ie80022cc60ed1f482b7593db5ef1ac1c5ea33d8d

M       buildSrc/src/main/kotlin/androidx/build/PublishDocsRules.kt
M       jetifier/jetifier/migration.config
M       settings.gradle
A       transition/transition-ktx/OWNERS
A       transition/transition-ktx/api/1.4.0-alpha01.txt
A       transition/transition-ktx/api/current.txt
A       transition/transition-ktx/api/public_plus_experimental_1.4.0-alpha01.txt
A       transition/transition-ktx/api/public_plus_experimental_current.txt
A       transition/transition-ktx/api/res-1.4.0-alpha01.txt
A       transition/transition-ktx/api/restricted_1.4.0-alpha01.txt
A       transition/transition-ktx/api/restricted_current.txt
A       transition/transition-ktx/build.gradle
A       transition/transition-ktx/src/androidTest/AndroidManifest.xml
A       transition/transition-ktx/src/androidTest/java/androidx/transition/TestActivity.kt
A       transition/transition-ktx/src/androidTest/java/androidx/transition/TransitionTest.kt
A       transition/transition-ktx/src/androidTest/res/layout/test_activity.xml
A       transition/transition-ktx/src/main/AndroidManifest.xml
A       transition/transition-ktx/src/main/java/androidx/transition/Transition.kt

https://android-review.googlesource.com/1172715

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 2e9f35536432bed0677171c8ae59b4f67850915a
Author: Jelle Fresen <jellefresen@google.com>
Date:   Fri Jul 12 14:26:10 2019

    Use double instead of float for decimal positions
   
    A position ranges from 0 to Integer.MAX_VALUE, but floats only have a 23
    bit mantissa. Values over 2^23 are rounded to a nearby value.
   
    Solve this by using double instead of float when we need to represent a
    position with a fractional component. A double has a mantissa of 52 bit
    and can therefore represent all 2^32 possible int values.
   
    Bug: 134858960
    Test: ./gradlew viewpager2:cC
    Change-Id: I08b97df6fac600caa83366ccab8671541e2c1e7f

A       viewpager2/src/androidTest/java/androidx/viewpager2/test/ui/SparseAdapter.kt
M       viewpager2/src/androidTest/java/androidx/viewpager2/widget/FakeDragTest.kt
M       viewpager2/src/androidTest/java/androidx/viewpager2/widget/OffscreenPageLimitTest.kt
M       viewpager2/src/androidTest/java/androidx/viewpager2/widget/PageChangeCallbackTest.kt
M       viewpager2/src/androidTest/java/androidx/viewpager2/widget/PageTransformerTest.kt
M       viewpager2/src/androidTest/java/androidx/viewpager2/widget/SetItemWhileScrollInProgressTest.kt
M       viewpager2/src/main/java/androidx/viewpager2/widget/ScrollEventAdapter.java
M       viewpager2/src/main/java/androidx/viewpager2/widget/ViewPager2.java

https://android-review.googlesource.com/1014538
https://goto.google.com/android-sha1/2e9f35536432bed0677171c8ae59b4f67850915a

Fixed in now released beta03 - https://developer.android.com/jetpack/androidx/releases/viewpager2#1.0.0-beta03