floschu / control Goto Github PK

https://pitest.org/

• Add pitest
• Increase mutation coverage

https://kotlinlang.org/docs/reference/multiplatform.html

• release multiplatform binaries

The Controller is not started lazily if only the controller.effects getter is called (and no other property such as the controller.state is accessed or controller.dispatch is being called).

There may be the start() logic missing here:

In a real world example, this would be relebant if e.g. in a transformer an onStart() with an emitEffect() should be called, which would then only be called after an action has been dispatched.

I'm just about to create a PR which adds a test for that as well as a possible fix, if the current behavior is not considered expected.

Starting with 1.0.0 add proper release notes.

• ensure binary compatibility across releases (e.g. via https://github.com/Kotlin/binary-compatibility-validator)
• add CHANGELOG.md
• safeguard develop (PR's only)
• publish first official release with changelog

Kotlin/kotlinx.coroutines#1973

• Consider using MutableStateFlow instead of ConflatedBroadCastChannel to back ControllerImplementation.state.
• Consider whether Controller.state and Controller.currentState should be replaced by StateFlow