fix Topology export

Fix for #27 and #28, Rabbus.Topology where was not exported, and documentation updated

rabbot v1.0.6 and documentation

this release updates to rabbot v1.0.6 and makes another major pass at cleaning up and improving the documentation.

additionally, docker is now used for the test suite with a full docker-compose setup to make things simple

migrate from wascally to rabbot

this is a major overhaul of many aspects, including the addition of a Topology object and migration from wacally to rabbot as the underlying library.

please see the upgrade guide and new documentation for full information on what has changed.

Bug Fixes For Middleware and messageType recommendation

This release contains several major bug fixes for #14 and #15.

Along with these fixed, Rabbus now recommends you do not use a messageType properties for message producers or consumers, with the exception of the Publisher and Subscriber objects. Due to a limitation that will hopefully be addressed soon, Pub/Sub requires either a messageType or routingKey.

I also added CONTRIBUTING.md and a CODE_OF_CONDUCT.md to the project.

If you're using v0.7.0, please upgrade to v0.7.1 immediately.

Middleware and Consumer API Overhaul

MAJOR BREAKING CHANGES

This release marks a significant change in the internals of Rabbus, completely replacing the middleware implementation with a library called generic-middleware to provide a more Express.js like middleware experience.

Because of this change internally, the external API has also been updated for middleware on both producers and consumers. Additionally, consumer methods to receive messages now follow the same middleware format.

With this change, receiving a message through a Rabbus object will no longer automatically ack or nack a message for you. Now, you must call actions.ack() or .nack() or .reject() as is appropriate for your situation.

Lastly, error handling has been greatly improved. You can now register an error handler middleware function, similar to Express.js error handlers. This provides much more flexibility and the ability to nack or reject a message on error.

For more information, see the upgrade guide.

updated whistlepunk logging library

• updated whistlepunk logging library to v0.3.2

Major Bug Fix; Add Logging

• fixed the request/response code that I had previously broken
• added basic logging via whistlepunk (same thing used in wascally)

Reduced Code, Custom Message Properties

This release sees major cleanup and consolidation of the code behind all of the producer/consumer pairs in Rabbus. The vast majority of the code has been reduced to the base producer / consumer objects, with each specific pair being configuration with appropriate method calls on top of them.

This will open opportunity for simplified code overall, and moving forward with a better API - more node-like w/ callbacks that get error as first param, etc.

Additionally, message producers can now publish custom message properties. See the readme for information on this.