All Versions
10
Latest Version
Avg Release Cycle
91 days
Latest Release
87 days ago

Changelog History

  • v2.4.0

    July 28, 2019
    • ⚡️ Kotlin updated to 1.3.40
    • ⚡️ RxJava updated to 2.2.10
    • Migrated to Gradle 5.4.1 and Gradle Kotlin DSL
  • v2.4.0-RC3

    July 12, 2019
  • v2.4.0-beta.1

    June 28, 2019
    • ⚡️ Kotlin updated to 1.3.40
    • ⚡️ RxJava updated to 2.2.10
    • Migrated to Gradle 5.4.1 and Gradle Kotlin DSL
  • v2.4.0-beta

    June 28, 2019
  • v2.3.0

    August 10, 2018

    🚀 This is the first release for RxKotlin in quite some time. I apologize it took so long.

    • ⚡️ RxJava updated to 2.2.0
    • ⚡️ Kotlin updated to 1.2.60
    • ⚠ Silence unused and platform warnings #179
    • ➕ Add missing @CheckReturnValue annoations #180
    • ➕ Add zero-arg flatMapIterable and concatMapIterable #185
    • 👉 Make cast and ofType operate on wildcard types rather than Any #176
    • ➕ Add Flowables.create with lambda as last parameter #188
    • 🔄 Change return type of Flowable.withLatestFrom #193

    Thank you everyone for your contributions!

  • v2.2.0

    November 27, 2017

    🚀 This is a breaking release removing some annoyances, specifically the toSingle() and toMaybe() extension functions targeting futures, callables, and even single T items.

    🚚 These caused far more harm than good, as they often clashed with other libraries and people's own extensions. For instance, RxKotlinFX has a Dialog<T>.toMaybe() extension which emits a dialog's response. This clashed directly with the toMaybe() in RxKotlin. Rather than deprecating these extensions, they were just removed to prevent further hindrance.

    🚚 Deprecated Observable#combineLatest() and its Flowable counterpart have been removed as well, and you can use the Observables and Flowables factories instead.

    ⚡️ RxJava and Kotlin dependencies have been updated as well.

  • v2.1.0

    June 24, 2017

    🚀 There are a number of changes in this release, some of which are possibly breaking. Many additions seek to expand the SAM helpers used to workaround the SAM issue.

    zip(), combineLatest(), zipWith(), and withLatestFrom() now support emitting Pairs and Triples when no combining function is provided for 2-3 source arguments. This applies to Observable, Flowable, Single, and Maybe types.

    Singles and Maybes have been greatly expanded to include more SAM helper operators for zip() and zipWith()

    toMap() and toMultimap() extension operators have been added to Observable<Pair<X,Y>> and Flowable<Pair<X,Y>>, which will automatically use each Pair emission to map the key and value without any arguments.

    🚚 Order of parameters for subscribeBy() have been moved so that onNext is the default if only one unnamed parameter is provided.

    Kotlin 1.2 and RxJava 2.1.0 are now dependencies

    🚀 Please file any issues if you have any questions or concerns. Thanks to everyone who contributed to this release.

  • v2.0.3

    May 18, 2017

    🚀 This is a quick release to remove Java 8 configuration, so this works on Java 6+.

    Also a blockingSubscribeBy() has been added as discussed here.

  • v2.0.2

    May 03, 2017

    🚀 This is a re-release of the features in 2.0.1 to address some build issues during deployment. combineLatest() also received extensions to work with Pair and Triple emissions.

    Thanks @stepango for putting these changes in.

  • v2.0.1

    May 02, 2017

    🚀 This release focuses on "workaround" fixes for the SAM conversion issue when using Kotlin with RxJava 2.x.

    Currently, the Kotlin compiler gets confused and cannot infer when presented with multiple SAM parameter overloads. Hopefully, JetBrains will resolve this issue sooner than later. Until then, we have put together some helpers to get us by:

    ✅ Non-SAM zip() and withLatestFrom() extension function operators were added to Observable, Flowable, Single, and Maybe where applicable.

    ✅ Observables, Flowables, Singles, and Maybes classes were added to house Kotlin-friendly non-SAM versions of zip() and combineLatest().

    This does not address all operators affected by the SAM issue, but these are commonly encountered and will serve as a good start. For instance, the subscribe() function on Single and Maybe will be addressed later as they may require a different method signature.

    Thanks to @chris-horner for spearheading this idea.