-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: support path-based arguments #764
Comments
I can see this being a useful feature. How would the different pattern matching syntaxes for RMQ/NATS/Redis/etc be handled? For example, RMQ supports either |
It was just a little thought to add in backlog, without any details. |
* feat (#764): Context dict keys, Path and Header objects * feat: check only exchange name at publish * feat: fast access to Message annotations * test: fix empty handler case * chore: refactor Test CI * chore: add distribution tests * chore: fix distribution tests * chore: fix real broker tests * lint: fix mypy * chore: fix coverage CI * docs (#682): fill publisher pages, add header, path sections * chore: fix CI merging * Add untracked files * Proofread docs and fix issues --------- Co-authored-by: Kumaran Rajendhiran <[email protected]>
Some brokers (RMQ, NATS, Redis, etc) allows you to consume messages by pattern
So, we can support path-based arguments in this case
The text was updated successfully, but these errors were encountered: