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.
Summary:
Release | What | When |
---|---|---|
• v0.3.1 | Extension Support with Logging Example | Mar 27, 2017 |
• v0.3.0 | Parameter Validation | Mar 13, 2017 |
• v0.2.0 | Added support for initialState | Mar 9, 2017 |
• v0.1.0 | Initial Release | Mar 8, 2017 |
Details ...
v0.3.1 - Extension Support with Logging Example (Mar 27, 2017)
Full Docs • GitHub Release • GitHub Content
NOTE: This release is a documentation enhancement only. The API is NOT impacted in any way.
The Dev Guide was refined to include Extending astx-redux-util along with an extensive Logging Extension section, showing how
reducerHash
can play a key roll in implementing a centralized reducer-based logging utility.A Most Excellent Example was streamlined, replacing the placeboReducer with an anonymous arrow function.
v0.3.0 - Parameter Validation (Mar 13, 2017)
Full Docs • GitHub Release • GitHub Content
Parameter validation is now performed on all function calls. Invalid usage results in thrown exceptions. NOTE: The API is NOT impacted in any way.
SideBar: Starting in this release, a distribution tarball (
astx-redux-util_{ver}tar.gz
) is promoted in the GitHub Releases Page, which contains various executable bindings and documentation (should you wish to retain the docs locally). Please refer to the Distribution section for more details.
v0.2.0 - Added support for initialState (Mar 9, 2017)
Full Docs • GitHub Release • GitHub Content
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, theInitialState
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 point).As is turns out, this simplifies the examples found in the astx-redux-util v0.1.0 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 astx-redux-util function.
v0.1.0 - Initial Release (Mar 8, 2017)
Full Docs • GitHub Release • GitHub Content
- Holy Guacamole Batman! ... This commit has no parents!!