Configuration option to specify Messenger transport
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 73
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
With the current implementation I have to manually add your commands to the messenger routing config to use an async transport. Instead it would be nice to have a configuration option named transport or something. This transport could then be used to route your messages.
I have done something similar here (although I think it's ugly): https://github.com/Setono/SyliusFragmentTranslationPlugin/blob/master/src/DependencyInjection/SetonoSyliusFragmentTranslationExtension.php#L36-L53
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current Messenger routing configuration and the linked SetonoSyliusFragmentTranslationPlugin DependencyInjection extension example. Determine how a transport option should route the plugin's messages, and consider the configuration and integration tests needed to show that the selected transport is used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100