forked from https://github.com/symfony/symfony
7497ad4a68
This PR was merged into the 4.1 branch. Discussion ---------- [Messenger] Allow to scope handlers per bus | Q | A | ------------- | --- | Branch? | 4.1 <!-- see below --> | Bug fix? | no | New feature? | yes <!-- don't forget to update src/**/CHANGELOG.md files --> | BC breaks? | no <!-- see https://symfony.com/bc --> | Deprecations? | no <!-- don't forget to update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tests pass? | yes <!-- please add some, will be required by reviewers --> | Fixed tickets | N/A <!-- #-prefixed issue number(s), if any --> | License | MIT | Doc PR | todo <img width="970" alt="screenshot 2018-05-15 a 18 34 11" src="https://user-images.githubusercontent.com/2211145/40070551-b36d1f50-586e-11e8-8a44-c6a1503312dd.PNG"> This prevents from dispatching a message in the wrong bus. It works especially great with PSR-4 discovery in DI: ```yaml command_handlers: namespace: App\Message\ resource: '%kernel.project_dir%/src/Message/*CommandHandler.php' tags: - { name: messenger.message_handler, bus: command_bus } query_handlers: namespace: App\Message\ resource: '%kernel.project_dir%/src/Message/*QueryHandler.php' tags: - { name: messenger.message_handler, bus: query_bus } ``` <details> <summary>(or in some layered architecture)</summary> ```yaml command_handlers: namespace: App\Application\ resource: '%kernel.project_dir%/src/Application/**/Handler/*CommandHandler.php' tags: - { name: messenger.message_handler, bus: command_bus } query_handlers: namespace: App\Application\ resource: '%kernel.project_dir%/src/Application/**/Handler/*QueryHandler.php' tags: - { name: messenger.message_handler, bus: query_bus } ``` </details> --- It also updates (and add tests for) the `DebugCommand`, so we can inspect easily where is supposed to be handled each message. It's totally optional, and if the bus isn't provided, then it stays available in every bus. Commits ------- |
||
|---|---|---|
| .composer | ||
| .github | ||
| src/Symfony | ||
| .editorconfig | ||
| .gitignore | ||
| .php_cs.dist | ||
| .travis.yml | ||
| appveyor.yml | ||
| CHANGELOG-4.0.md | ||
| CHANGELOG-4.1.md | ||
| composer.json | ||
| CONTRIBUTING.md | ||
| CONTRIBUTORS.md | ||
| LICENSE | ||
| link | ||
| phpunit | ||
| phpunit.xml.dist | ||
| README.md | ||
| UPGRADE-4.0.md | ||
| UPGRADE-4.1.md | ||
| UPGRADE-5.0.md | ||
Symfony is a PHP framework for web applications and a set of reusable PHP components. Symfony is used by thousands of web applications (including BlaBlaCar.com and Spotify.com) and most of the popular PHP projects (including Drupal and Magento).
Installation
- Install Symfony with Composer (see requirements details).
- Symfony follows the semantic versioning strictly, publishes "Long Term Support" (LTS) versions and has a release process that is predictable and business-friendly.
Documentation
- Read the Getting Started guide if you are new to Symfony.
- Try the Symfony Demo application to learn Symfony in practice.
- Master Symfony with the Guides and Tutorials, the Components docs and the Best Practices reference.
Community
- Join the Symfony Community and meet other members at the Symfony events.
- Get Symfony support on Stack Overflow, Slack, IRC, etc.
- Follow us on GitHub, Twitter and Facebook.
Contributing
Symfony is an Open Source, community-driven project with thousands of contributors. Join them contributing code or contributing documentation.
Security Issues
If you discover a security vulnerability within Symfony, please follow our disclosure procedure.
About Us
Symfony development is sponsored by SensioLabs, led by the Symfony Core Team and supported by Symfony contributors.