Skip to content

Latest commit

 

History

History
129 lines (70 loc) · 4 KB

Change-Log.md

File metadata and controls

129 lines (70 loc) · 4 KB
Raw

🏠 Home

Dynadux - Change Log

Compliant with SemVer spec.

v1

v1.1.0

First release

v1.2.0

Multiple reducers per action
  • The reducers config property, can be not only a dictionary but an array of dictionaries.

v1.3.0

debug middleware improvements
  • dispatch method
  • better timestamp
  • configurable global variable name

v1.4.0

onDispatch new callback
  • Store has now a new onDispatch callback to "listen" store's dispatches
debug middleware improvements
  • new state getter for the current state
  • new listPayloads list that includes the payloads
  • new list column with the elapsed time for reducer's execution

v1.5.0

New Feature Sections

Sections simplifies the creation of root properties of apps or big components.

v1.7.0

IDispatchConfig: Stores's dispatch() method 3rd argument

Reducer's dispatch method accepts as 3rd argument a configuration object of IDispatchConfig interface.

Currently, this interface has only the triggerChange: boolean with default value true.

Setting the triggerChange to false a dispatch can ask from Dynadux to do not trigger the change.

Reducer's API offer the blockChange() method

Inside reducer's (action's) implementation, Dynadux is offering the blockChange() method. In this way, reduce itself can block the onChange call.

v2

v2.0.0

Improvement: Debugger's configuration change

With this breaking version, only the Debugger's Configuration is changed.

The globalVariableName config property has been renamed to debuggerStoreName, and it is required.

Now, the debugger would always be included in the Stores, even in production, since the debugger is activated only when the debuggerStoreName is not an empty string.

For more read the Debugging section.

v2.0.2

Improvement: Simpler name

The dispatch's config prop triggerChange is renamed to blockChange with opposite logic.

The triggerChange has still backward compatibility with console warn till next major release.

v2.2.0

Feature: add/removeChangeEventListener for Store and Sections

You can register/unregister listeners for Store's or Section's changes.

The events approach is a kinda anti-pattern for state managers and for Dynadux as well. So it is not encouraged to use them, so they are not documented at least at the moment. Events are not going to be removed and are stable.

Events are used internally to support the react-dynadux.

Feature: Support React Provider react-dynadux

createStore result also returns the provider property, needed by the react-dynadux.

v2.4.0

Fix: Catch reducers errors

Catches the errors from middlewares and reducers, since uncaught errors block later dispatches.

The error is now consoled.

v2.4.5

Improvement: Array of middlewares

middlewares array accepts false, null and undefined values for inline comparison (ternary operators).

v2.5.5

Fix: Overloaded action without result blocks the change

An action can be overloaded. That means a reducer of another Section can implement the same action.

This allows actions to be used as events.

There was a bug where if an implementation of an overloaded action return no change, the change wasn't applied.

Read more