UI Composition - versioned doc dir

Segregate versioned doc dir from code changes (allowing diffs of code modification only)

UI Composition

Full Docs • GitHub Release • GitHub Content • Diff • Migration Notes

NOTE: This release contains breaking changes from prior releases. A retrofit of client code is necessary (see the Migration Notes link above).

1. Review: New UI Composition

   Beginning with feature-u V1 Cross Feature Communication has been completely re-designed to include UI Composition as a core offering of feature-u (thanks {{book.ext.jeffbski}} for the design collaboration)!

   • This refactor promotes one solution for all Cross Feature Communication (i.e. Actions, Selectors, UI Components, API, etc.), making it comprehensive and universal.

   • This is an extremely powerful enhancement, and even extends to things like Feature Based Routes.

   • It represents a significant step forward in providing seamless feature-based development!

   At a high level, the following items have been impacted (more detail can be found at Cross Feature Communication):

   • In an effort to standardize terminology (and remove ambiguity), the term fassets (feature assets) is being used throughout, replacing publicFace (on the aspect definition side) and app (on the usage side).

   • The Feature.fassets aspect replaces Feature.publicFace, providing a more formal set of directives, supporting things like contractual arrangements (of usage and definition), and validation of resources.

   • The fassets object replaces the app object, to programmatically access cross-feature resources.

   • The managedExpansion() function has been renamed to expandWithFassets().

   • The new withFassets() higher-order component (HOC) auto-wires named feature assets as component properties.

   In addition, if you are using any of the feature-u extended aspect plugins, you must install the latest version, as they now pass through the new fassets object.

2. Docs: Documentation improvements include:

   • The docs have been enhanced in several areas, including API clarifications, improved cross-navigation between API/Guide, additional points of interest, examples, etc. Take a peek (always improving).

   • Several diagrams have been added to the docs. You know what they say: "a picture is worth a thousand words"!

   • Our docs now employ a dynamic left-nav menu, that only exposes sub-sections of the active section. As a result, we now promote more left-nav sub-section links, improving the visualization of "where you are at" in larger topics.

Establish Polyfill Strategy - versioned doc dir

Segregate versioned doc dir from code changes (allowing diffs of code modification only)

Establish Polyfill Strategy

NOTE: This release is a non-breaking change (i.e. no API was affected).

1. Review: A new policy is in affect where polyfills are the responsibility of the client app, when the target JavaScript engine is inadequate (such as the IE browser). Please refer to Potential Need for Polyfills for more information.

   As a result, all previous code patches related to es2015+ polyfill issues were removed, in favor of polyfilling at the app-level.

2. Internal: The most current babel version/configuration is now used to transpile the library's es5 distribution.

3. Internal: The most current docs version/configuration (i.e. GitBook, JSDoc) is now used to generate our documentation.

Initial Release - versioned doc dir

Segregate versioned doc dir from code changes (allowing diffs of code modification only)

Initial Release

This is where it all began ...

1. Holy Guacamole Batman! ... This commit has no parents!!