no-rxstate-imperative-in-reactive
Warns against mixing imperative RxState methods in reactive methods.
Rationale
Inconsistent mixing of reactive and imperative usage should be avoided in RxState. Using an imperative method (state#set
or state#get
) in the context of a reactive method (state#hold
or state#connect
) is a confusing mixing of paradigms, when there is usually a better solution available. E.g. calling state#set
in state#hold
may be replaced with the more declarative state#connect
.