This project adheres to Semantic Versioning. Each release, along with migration instructions, is documented on this page. Please Note: The Revision History found here ONLY covers the history up to this release. In order to view ALL Revision History, please refer to the latest astx-redux-util release, or the Github Release Notes.
|• v0.2.0||Added support for initialState (Mar 9, 2017)|
|• v0.1.0||Initial Release (Mar 8, 2017)|
v0.2.0 - Added support for initialState (Mar 9, 2017)
This release adds support for the
InitialState parameter in each of
the reducer composition utilities.
This parameter optionally defines the fall-back state value used during the state initialization boot-strap process.
In general, redux expects your state to have concrete values
(i.e. something other than
undefined). This means that the
reduction entry point to each state element should define a default.
Keeping this in mind, the
InitialState parameter is optional,
because some reducers are "by design" (when combined in a composition)
intended to be mid-stream processors (i.e. NOT the reduction entry
As is turns out, this simplifies the examples found in the
release, in that NO app-supplied wrapper function is needed for the
sole purpose of providing this initial value ... rather: the
InitialState can be specified directly as a parameter to the
v0.1.0 - Initial Release (Mar 8, 2017)
Holy Guacamole Batman! ... This commit has no parents!!