Hooks and Aspect Plugin Changes

Full Docs • GitHub Release • GitHub Content • Diff

NOTE: This release contains minor breaking changes from prior releases. A trivial retrofit of client code may be necessary (depending on your usage).

1. Changed: For redux users, the Application Life Cycle Hooks that promote the redux appState parameter, are now being passed the redux getState function. To obtain the appState you merely invoke: getState(). This gives async long-running processes access to the most current state changes (over time) ... thanks @sylvainlg!!

   Please Note: Prior to this release, these parameters were promoted directly by feature-u (using conditional logic that detected the feature-redux aspect). This coupling has been removed. These parameters are now promoted though the feature-redux aspect, using the new Aspect.injectParamsInHooks() hook (mentioned below). As a result, you must update feature-redux to V3 or greater.

2. Added: For Aspect Extension users, a new Aspect.injectParamsInHooks() Aspect Life Cycle Method has been added that allows the Aspect to promote namedParams into the feature's Application Life Cycle Hooks.

3. Changed: For Aspect Extension users, Aspect Plugins no longer have one specific method that is required. Rather the requirement is to specify something (so as to not have an empty plugin that does nothing). Please refer to the "No Single Aspect Method is Required" discussion in the Aspect Life Cycle Methods.

4. Docs: Documentation improvements include:

   • For Aspect Extension users, a new section was added that highlights how Custom Aspect Plugins are typically promoted through a constructor.