Prepare for 0.2.0

[ZacSweers]

• New: Kotlin artifact! (Add kotlin module #47)

This adds autoDisposeWith() extensions to RxJava types.

myObservable
   .doWhatever()
   .autoDisposeWith(this)
   .subscribe()

• New: Plugin system! (Add plugin API for handling OutsideLifecycleExceptions. #57)

Modeled after RxJava's plugins, this allows you to customize the behavior of AutoDispose with lifecycle boundary checks.

AutoDisposePlugins.setOutsideLifecycleHandler(t -> {
    // Swallow the exception, or rethrow it, or throw your own!
})

A good use case of this is, say, just silently disposing/logging observers outside of lifecycle exceptions in production but crashing on debug.

• New: Test helpers! (Adding TestLifecycleScopeProvider. #48 TestScopeProvider + build fixes #49)

Two helpers were added to simulate conditions in testing.

• TestLifecycleScopeProvider
  • This has two corresponding lifecycle methods: start() and stop()
• TestScopeProvider
  • Has just one method - emit().

For testing with just the Maybe<?> scope, we recommend using RxJava's built-in MaybeSubject.

• Fix: Fixed a race condition where upstream wouldn't be disposed if the lifecycle emitted or error'd synchronously (i.e. was already terminated). (Add plugin API for handling OutsideLifecycleExceptions. #57)
• Fix: Add missing @CheckReturnValue annotations to subscribeWith methods. (Add CheckReturnValue annotations to subscribeWith #53)

Other tidbits:

• Removed @NonNull annotations. Everything is @NonNull by default, and only elements
  annotated with @Nullable are not.
• Use of the new java-library plugin for gradle (Update to java-library plugin #64). The RxJava dependencies are marked as api.
• Error prone has been integrated. Currently the annotations are just marked as compileOnly, but if a need arises/community wants them - we can compile them in a future version.

[ZacSweers]

@tonycosentini @LukeStClair @uber/mobile-platform-android if this all looks good, we can cut a release monday or tuesday

[AttwellBrian]

New: Plugin system! (#57)

Nice idea. Why do we need setOutsideLifecycleHandler when we already have the ability to RxPlugins to suppress this errors with RxPlugins?

[tonycosentini]

It's a bit easier to integrate. If you take a look at the current implementation in our error handler, it's a pretty fragile process to properly pull out the lifecycle exceptions when they are already wrapped in multiple exceptions.

…

On Mon, May 8, 2017 at 9:58 AM Brian Attwell ***@***.***> wrote: New: Plugin system! (#57 <#57>) Nice idea. Why do we need setOutsideLifecycleHandler when we already have the ability to RxPlugins to suppress this errors with RxPlugins? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#68 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABbq7QxJhpeN1e0W5vhb6QgCh-Y_V-wks5r30m8gaJpZM4NS9sQ> .

[ZacSweers]

Released!