ReleaseNotes0_5_5

Mojito Release 0.5.5

Mojito 0.5.5 is now tagged and available on npm. List of changes between 0.5.4 and 0.5.5 here.

Features

• Global models thru ac.models.expose() upgraded from experimental to beta
• Support for handlebars helpers thru mojito-helpers-addon and support for global handlebars helpers thru ac.helpers.expose() (experimental feature, more info !(here)[/yahoo/mojito/pull/1011])
• Upgrading to [email protected]
• Introducing error propagation in mojito-composite-addon by using the flag propagateFailure in a child.
• Improved Store to minimize memory footprint.
• Introducing a clear separation between YUI core modules and app yui modules. YUI Core modules will not be served from the app origin server unless the staticHandling.serveYUIFromAppOrigin flag is set to true in application.json. This change minimize the initial footprint of the app as well as offline capabilities when using mojito build html5app command. More info !(here)[/yahoo/mojito/pull/997].

Important note about potential backward compatibility issues

In this release we introduced some performance optimizations, as a result some internal APIs changed, and this will potentially impacting 3rd party components that are using protected or internal store APIs. This is the case of [email protected], a new version of shaker will be released very soon to address these changes, in the meantime, you can follow this PR: https://github.com/yahoo/mojito-shaker/pull/43.

Fixes

• Fixed issue #293. HTMLFrameMojit should honor child metas
• Fixed hybrid build issue #1006
• Fixes issue #865. Fixes issue #25: mojito-composite-addon error propagation
• Fixed lingering occurances of store.yui.getConfigAllMojits()
• Fixes the Cache-Control for static assets.
• Supporting html5app, forceRelativePaths for yui loader, making root and base to be relative when needed.
• (sweetandsour2) Fix for client side hooks, bug fix in template hooks.