62 consumer route pattern matching

[lamchakchan]

Description

Fixed the bug around wildcards and RMQ subscriptions. The initial implementations allowed for wild cards (#, *) to be used against the consume interface of RMQ. But when messages were sent back down stream to bunnyBus, the routes did not match the routes used with the handlers set in the subscription call because logic was not implemented to do any wild card substitutions. To support this, pattern matching logic had to be written around dynamic regex generation. A lot of test were put in place to prove the rigor of the runtime for this bug fix.

Related Issue

• Improve the pattern matching around the subscription routeKey #62

Motivation and Context

While no messages were ever lost when a message was subscribed down and missed by the handler because by default, bunnyBus forwards all messages with processing issues to the error queue; we do want to make sure the subscriber runs in parity with the route key binding language of RMQ.

Types of changes

• Documentation only (no changes to either lib/ or test/ files)
• Bug fix (non-breaking change which fixes an issue. you didn't modify existing tests)
• New feature (non-breaking change which adds functionality. you added at least one new test)
• Breaking change (fix or feature that would cause existing functionality to change. you had to modify existing tests.)

Checklist:

• I have read the CONTRIBUTING document.
• My code follows the Hapi.js style guide.
• I have updated the documentation as needed.
• I have added tests to cover my changes.
• All new and existing tests passed.