Behaviors

Version 1.7 represents a significant step in formalizing the ways to improve your view code though reusable behaviors. Say goodbye to custom mixin strategies and welcome behaviors into town.

• Behaviors

  A Behavior is an isolated set of DOM / user interactions interactions that can be mixed into any View. Behaviors allow you to blackbox View specific interactions into portable logical chunks, keeping your views simple and your code DRY. Read the docs here.

• Modules

  • Call stop listening on module stop.

• Events

  • add a before:show event for views and regions

• Docs

  • Entire refactor of application docs.

• Tests

  • Rework the module tests to improve readability and consistency.

• General

  • switch from ~ to ^ for trusted dependencies.

Bug fix

• Fixes
  • Patches a bug that would cause modules to be initialized twice when a custom module class is passed

improvements!

• Improvements

  • Enable more direct module instantiation on Marionette.App.

      var ItemModule = Marionette.Module.extend({
        startWithParent: false,
        initialize: function(options) {},  
        onStart: function() {}
      });
    
      // ...
    
      this.app.module('Items', ItemModule);

  • ui hash interpolation now supports a functional ui hash.

      ui: function() {
        return {
          "click @ui.foo": "attack"
        }
      }

• Fixes

  • Fix @ui interpolation for handling complex selectors.

      {
        "click div:not(@ui.bar)": "tapper"
      }

  • Bump backbone.babysitter and backbone.wreqr versions.

• General
  • Improve readme docs for CollectionView, AppRouter and ItemView.
  • Handle THE npm self sign cert problem
  • Replace unneeded argument slicing.
  • Normalize error throwing to use internal throwError helper method.
  • Use _ type checks for non performant code to improve readability and consistency.

ItemEvent Improvements + Better Module Docs.

v1.6.2 view commit logs

• CollectionView/CompositeView
  • allow itemEvents to use string based method names PR 875
• Modules
  • update module initialize to include moduleName and app PR 898
• General
  • significantly improve module documentation PR 897

v1.6.1 module bug fix

Modules

• Fix a bug where a module would not start by default when defined as an object literal

v1.6.0 - better modules

CompositeView

• add a composite:collection:before:render event

CollectionView

• checkEmpty can now be overridden

Modules

• Modules can now be created using the extend method, and then attached to an Application.

General

• add a component.json file
• update bower.json
• add AMD build in bower.json

Tests

• general clean up
• add sinon.js for test spys

v1.5.1 - bug fix

• CollectionView/CompositeView
  • Fix bug where show and onDomRefresh was not called on itemViews in certain conditions

v1.5.0

View

• View options can now be a function
• onDomRefresh is now only called when said view is in the DOM

CollectionView/CompositeView

• itemViewContainer is now called with the correct context
• Fix bug where reseting a collection within a collectionView would cause onShow and onDomRefresh to be called incorrectly on the itemViews.
• addItemView now returns the view that was added
• You can now specify an itemEvents hash or method which allows you to capture all bubbling itemEvents without having to manually set bindings.

itemEvents: {
  "render": function() {
    console.log("an itemView has been rendered");
  }
}

Region

• Region close event now passes the view being closed with the event.

General

• Updated bower ignore folder
• Added an editor config file

View Option Bug Fix

Fixes issue with a views class default options being removed on class instantiation.

raised in #808

v1.4.0 – UI hash cross utilization

adds the ability to DRY up your events and triggers as documented below

ui:
  button: '.button'

triggers:
  'click @ui.button': 'bam'

events:
  'click @ui.button': 'onButtonClick'