1.4.0

What's Changed

• Moved whatsnew.md to root and renamed to CHANGELOG.md by @LachlanMcKee in #169
• Update kotlin to 1.6.21 by @LachlanMcKee in #162
• Use version catalog by @LachlanMcKee in #171
• Added lint & detekt plugins by @LachlanMcKee in #172
• Use detekt.basePath instead of changing paths manually by @LachlanMcKee in #174
• Update Kotlin to 1.7.10 by @LachlanMcKee in #173
• Updated RxJava and RxKotlin to latest versions by @LachlanMcKee in #176
• Updated AndroidX libs and target sdk to 33 by @LachlanMcKee in #177
• Added tests for binder lifecycle extensions by @LachlanMcKee in #178
• Introduced LifecycleExtensions overloads to set observation schedulers by @LachlanMcKee in #179
• Fixed stability of workflow instrumentation tests by @LachlanMcKee in #181
• Add junit5 dependency by @EnderErol in #180
• Updated changelog for version 1.4.0 by @LachlanMcKee in #182

New Contributors

• @EnderErol made their first contribution in #180

Full Changelog: 1.3.1...1.4.0

1.3.1

(#138):
Fixed regression related to BaseFeature actor.

The Actor subject was made serializable, and was also using a flatMap. Both of these changes caused a change in behaviour relating to the ordering of news (in features that have a PostProcessor which triggers extra actions).
This change was made as part of introducing the optional FeatureScheduler to BaseFeature.

If you provide a FeatureScheduler and use a PostProcessor, please be aware that the ordering of your news could change.

The previous news ordering behaviour is actually a bug in BaseFeature caused by recursion, and will hopefully be addressed (as an opt in change) in a future release.

1.3.0

(#147):
Introduced 'async' feature which is moves work to a dedicated single-threaded feature scheduler, while being observable on the observation scheduler

(#148):
Updated mockito-kotlin library.

(#150):
Fixed Bootstrapper variance.

(#150):
Minor improvements to the new 'async' feature.

(#158):
Introduced an optional FeatureScheduler which can be used with non-async features.
This is useful when a feature is instantiated on a thread other than the thread it should be bound to (for example the UI thread).

When providing a FeatureScheduler, the feature is able to correctly switch to its desired thread rather than throwing an exception.

(#160):
Changed to Java 8 compatibility

(#161):
Improved the error message thrown by SameThreadVerifier. It now includes the feature's class name and the thread names.