v1.5.1

• Fix API Documentation link in the README

v1.5.0

• It is possible that if the same client subscribes to the same URI multiple times at the same time, then the WAMP broker might given both subscriptions the same subscription ID
• swampyer can now handle this case and will call all handlers for the same subscription ID if an event occurs
  • The subscribe() method now returns an object with the subscription ID and the original subscription handler itself
    • This will be useful for uniquely unsubscribing a given handler while leaving any other subscriptions on the same subscription ID unchanged
  • The unsubscribe() method can now take the object returned by subscribe() and only unsubscribes the given handler by default
    • If there was only 1 handler for the subscription ID or if the unsubscribeAll argument is set to true then it will initiate a full unsubscribe from the WAMP router
    • Otherwise, it will just remove the handler from the list of handlers to call when an event occurs on the given subscription ID

v1.4.3

• Add reasonable defaults for args, kwargs, and details for reg/sub handlers

v1.4.2

• Simplify error handling from registration handlers
• Console log unhandled errors from registration and subscription handlers

v1.4.1

• Improve handling of errors inside registration handlers and forward them to the caller
• Improve types for the registration handler and subscription handler so that they are easier to use

v1.3.1

• The auth.onChallenge option for all the open* methods can now either be synchronous (as before) or asynchronous (the newly added functionality)
• Swampyer specific errors no longer extend Error
  • This means that they should show up as interactive objects in most browsers and should not get formatted (which happens if your error class extends Error). With WAMP operations it can often be useful to see the full error object
  • I have also added a toString() method to the SwampyerError base class so that String(anySwampyerErr) can still return some meaningful text.

v1.3.0

• It is a lot clearer way to stop automatic reconnections compared to the previous way of doing it
  • Previously we had to set the autoReconnectionDelay option and return null from it in order to stop automatic reconnections
  • But this meant that the developer also had to worry about returning valid delay values for cases where they did not want to stop automatic reconnection
• Updated tests
• Updated README
• Bumped version to 1.3.0

v1.2.1

Merge pull request #3 from zaberSatnam/master

Add CI