Skip to content

Releases: marionettejs/backbone.radio

v0.9.0

28 Jan 05:38
Compare
Choose a tag to compare
  • Breaking change: Space-separated requests no longer return an Array. Instead, an Object is returned.

    // old
    myChannel.request('thingOne thingTwo');
    // => [replyOne, replyTwo]
    
    // new
    myChannel.request('thingOne thingTwo');
    // => { thingOne: replyOne, thingTwo: replyTwo }
  • New feature: Radio.reset() is now a top-level API method that can be used to reset a channel, or all channels. Do note that channels continue to have their own reset method.

  • New feature: Radio.debugLog() is now exposed...go forth and customize how Radio logs potential errors!

v0.8.5

28 Jan 03:40
Compare
Choose a tag to compare
  • Bugfix: Fixes a bug where requesting multiple things at once could return a nested array of responses. For more, refer to #196.

v0.8.4

03 Jan 03:21
Compare
Choose a tag to compare
  • console.warn is only called internally if it exists

v0.8.3

01 Dec 01:31
Compare
Choose a tag to compare

The Backbone dependency has been updated to accurately reflect our support for versions only that are only greater than 1.0.0. We're also now testing against all supported Backbone and Underscore versions.

Thanks @megawac!

v0.8.2

30 Oct 03:23
Compare
Choose a tag to compare

This update makes Backbone.Radio compatible with Underscore as far back as 1.4.4. This was done primarily because Marionette supports back to 1.4.4.

v0.8.1

27 Oct 03:48
Compare
Choose a tag to compare

Fixes a bug where stopReplying and stopComplying would not remove the correct handlers given certain arguments.

v0.8.0

26 Oct 01:36
Compare
Choose a tag to compare

View change summary

DEBUG warnings when overwriting callbacks

When you overwrite a Request or Command in debug mode you will now get a warning.

// Turn on debug mode
Backbone.Radio.DEBUG = true;

// Register a reply
Backbone.Radio.reply('myChannel', 'someReply', 2);

// Overriding it will send a warning to the console!
Backbone.Radio.reply('myChannel', 'someReply', 5);

stopReplying and stopComplying now support the second and third arguments

The big change here is that the removal methods are more powerful, as they now support the same arguments as off. This gives you finer-grained control over the things that you unregister. You can, for instance, unregister by callback, or by context.

// Remove all callbacks with the context of 'this'
myChannel.stopComplying(undefined, undefined, this);

v0.7.2

26 Oct 01:00
Compare
Choose a tag to compare

Updates Underscore dependency in bower.json.

v0.7.1

26 Oct 00:52
Compare
Choose a tag to compare

Updates the Underscore dependency – thanks @megawac!

v0.7.0

02 Oct 21:02
Compare
Choose a tag to compare
v0.7.0