Skip to content

[Messenger] Rename the middleware tag #26862

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

Merged
merged 1 commit into from
Apr 9, 2018

Conversation

sroze
Copy link
Contributor

@sroze sroze commented Apr 8, 2018

Q A
Branch? master
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets ø
License MIT
Doc PR symfony/symfony-docs#9437

After a using it for a bit of time, it's weird to have the messenger.message_handler tag while using the message_bus_middleware tag for the middlewares.

I propose to rename the tag from message_bus_middleware to messenger.bus_middleware to keep some consistency.

@sroze sroze added this to the 4.1 milestone Apr 8, 2018
@sroze sroze merged commit dd18445 into symfony:master Apr 9, 2018
sroze added a commit that referenced this pull request Apr 9, 2018
This PR was merged into the 4.1-dev branch.

Discussion
----------

[Messenger] Rename the middleware tag

| Q             | A
| ------------- | ---
| Branch?       | master
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | ø
| License       | MIT
| Doc PR        | symfony/symfony-docs#9437

After a using it for a bit of time, it's weird to have the `messenger.message_handler` tag while using the `message_bus_middleware` tag for the middlewares.

I propose to rename the tag from `message_bus_middleware` to `messenger.bus_middleware` to keep some consistency.

Commits
-------

dd18445 Rename the middleware tag from `message_bus_middleware` to `messenger.bus_middleware`
@sroze sroze deleted the rename-middleware-tag branch April 9, 2018 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants