Housekeeping

This release removes the jQuery plugin from the repository, but doesn't make ANY changes to the API of the library, and has therefore not become a MAJOR release.

The motivation for the housekeeping was to make it easier for contributors to get their pull requests merged, by not having to battle obsoleted dependencies (buster, jslint, phantomjs).

Changes

• Remove jQuery plugin. Users that want to continue to use PubSubJS through jQuery, can use [email protected]
• Simplified test setup to use mocha
• Replace obsoleted jslint version (could not install on Travis anymore) with latest eslint

Bug fix: unsubscribe hierarchy

This release has a minor bug fix to unsubscribing hierarchies.

From #97

PubSub.subscribe('a', myFunc1);
PubSub.subscribe('a.b', myFunc2);
PubSub.subscribe('a.b.c', myFunc3);

PubSub.unsubscribe('a.b');
// no further notications for 'a.b' and 'a.b.c' topics
// notifications for 'a' will still get published

Thanks to @jbutz for the investigation and the fix

v1.5.2

Fixes an issue #71 with clearing subscriptions by the topic, making it match the documentation https://github.com/mroderick/PubSubJS#clear-all-subscriptions-for-a-topic

v1.5.1

Fixes an issue with immediateExceptions not working with namespaces #75

v1.5.0

• Add clearSubscriptions method that clears all subscriptions
• Add option to unsubscribe all subscriptions for a topic, via PubSub.unsubscribe('mytopic');
• #64 makes it possible to build the jQuery version without ruby dependency
• Fixes issues #49 and #51, by using commonjsStrict from UMD

Minor bug fix: call all subscribers and Buster upgrade

• Fix compatibility with BusterJS 0.7.4+
• Fix #43, where not all subscribers would be called, if one or more unsubscribed during publishing

Bug fix: topic propagation with hierarchical addressing

This release fixes a bug where more specific topic subscribers (rabbit.jumped) would not get notified if a top level subscriber (rabbit) didn't exist.

Remove version and name properties

Since PubSubJS is now available through both npm and bower, it's easy enough to programmatically determine which version you have, so I've removed the version and name properties from the PubSub object.

Bugfix, increased compatibility with SnapEngage

• Fixes #29, where subscribing non-functions would cause exceptions during publish. Reported by @m-btts
• Increased compatibility with websites using SnapEngage (#28), thanks to @joscha
• Added versioning script, to keep things aligned when tagging a new version. (Thanks @spmason)

Fix issue 26, and semver

Fixes #26

This release is recommended for everyone