All Versions
148
Latest Version
Avg Release Cycle
66 days
Latest Release
302 days ago

Changelog History
Page 1

  • v4.1.2

    April 21, 2019

    🔊 v4.1.2 view commit logs

    🛠 Fixes

    • 🏗 Error in the build's version number.
  • v4.1.1

    April 21, 2019

    🔊 v4.1.1 view commit logs

    🛠 Fixes

    • 🏗 Error in the build
  • v4.1.0

    April 20, 2019

    🔊 v4.1.0 view commit logs

    🔋 Features

    • CollectionView#addChildView now accepts a preventRender option.
    • 0️⃣ Marionette now uses el.ownerDocument.documentElement; by default instead of document.documentElement for querying, customizable via DomApi.getDocumentEl.
    • 🏗 The UMD build now reinstates noConflict for using multiple versions on the global scope.

    🛠 Fixes

    • 🛠 Fixed a case where a child view could potentially get multiple destroy events.
    • Pre-rendered views from outside of a region will now correctly empty an current view in a region if shown.
    • CollectionView's emptyView will now respect the childViewContainer for attachment.

    Misc

    • ⚡️ Updated backbone dependency to allow for 1.4 without a warning.
    • ⚡️ Tooling and testing was updated and improved removing gulp.
    • 🚀 Region._setElement was added for internal use, but may be made public in a future release.
  • v4.0.0

    August 06, 2018

    🔊 v4.0.0 view commit logs

    💥 Breaking Changes

    ⬆️ The breaking changes are documented in the upgrade guide.

    🔋 Features

    • 🚚 CollectionView can now render a template in the same fashion of the removed CompositeView.
    • View#triggers now passes the originating DOM event object as the final argument of the triggered Mn event.
    • View classes now have the bindRequests and unbindRequests API.
    • 📦 The ES6 package was exposed in package.json on jsnext:main
    • ⚡️ The underscore dependency was updated to include 1.8.3 - 1.9.x.

    📚 Documentation

    📚 The documentation structure was overhauled to provide a flow to reading through the docs.

  • v3.5.1

    November 09, 2017

    🛠 Fixes

    • View entity events set in initialize were being undelegated if modelEvents or collectionEvents were undefined.
  • v3.5.0

    November 05, 2017

    🔋 Features

    • NextCollectionView's filter event now returns the attaching and detached views.
    • 🚚 unbindEvents and unbindRequests can now be called without handlers to remove all handlers from an entity.

    🛠 Fixes

    • 🚚 If an event handler on a behavior was undefined it would remove any prior defined handler.
    • When a behavior is destroyed it will now undelegate the behavior events and triggers.
    • 🐎 When a view was added a performance check on NextCollectionView would sometimes prevent existing views from sorting correctly.
    • NextCollectionView viewFilter will now be called with the same arguments with underscore or lodash.

    🗄 Deprecations

    • Multiple handlers for a single event. If needed, use a single handler to call multiple methods.
  • v3.4.4

    October 03, 2017

    🛠 Fixes

    • 👻 Prevent exception when a view is instantiated with a non-existing selector el.
    • 🐎 When a collection defines the NextCollectionView sort order, the add at end performance improvement was removed to prevent edge case errors.
    • NextCollectionView no longer sorts according to the collection if sortWithCollection is set to false.
    • When views added to NextCollectionView from a collection don't have a matching model, removing the model no longer throws an error.

    Misc

    • ⚡️ NextCollectionView now uses backbone update flags instead of calculating changes for sorting
  • v3.4.3

    September 06, 2017

    🛠 Fixes

    • 🚚 NextCollectionView collection single model remove no longer incorrectly removes all children
    • EmptyView will correctly display if a NextCollectionView is rendered in initialize