[StateManager] - state and event, a third possibility

[b-ma]

Currently the StateManager can handle two type of data flow:

• states - the value is considered valid in time, only changes of the value are handled. Setting to the same value is therefore ignored and the subscribe callbacks are not executed.
• events - the value is a pure event (a point in time), .get('eventName') returns null, the value is only valid in asubscribe` callback. As such a event can trigger the same value multiple times.

We have a third possibility in between where we would like to be able to define a parameter that:

• does not check if the value has changed.
• re-trigger the subscribe callbacks each time a set call is made.

(@aside - this also shows that the component is not properly named)

[b-ma]

fixed in 3.1.0-beta

see filterChange options in params definition (defaults to true for backward compatibility)

[b-ma]

deployed in 3.1.0