Skip to content

[Messenger] Fix routable message bus default bus #31472

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
May 11, 2019

Conversation

weaverryan
Copy link
Member

Q A
Branch? 4.3
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets none
License MIT
Doc PR not needed

In #31288, we gave the RoutableMessageBus a "default" bus. We did that by using the MessageBusInterface service in the locator. But, no such service exists - I think that was just a huge oversight (and maybe @dirk39 named a bus this in the project he was testing on?). The services in the locator are very simply the keys under framework.messenger.buses or the default, which is a single messenger.bus.default id. There is an alias in the container for MessageBusInterface, but this is not added to the locator (and adding it would be a bit awkward, as MessengerPass is in the component and the interface alias is entirely a framework thing).

Cheers!

@weaverryan weaverryan force-pushed the messenger-fix-routable-message-bus branch from 917d72c to 42e0536 Compare May 10, 2019 17:35
@weaverryan weaverryan added this to the 4.3 milestone May 10, 2019
@Tobion
Copy link
Contributor

Tobion commented May 11, 2019

Thanks for fixing this bug @weaverryan.

@Tobion Tobion merged commit 42e0536 into symfony:4.3 May 11, 2019
Tobion added a commit that referenced this pull request May 11, 2019
This PR was merged into the 4.3 branch.

Discussion
----------

[Messenger] Fix routable message bus default bus

| Q             | A
| ------------- | ---
| Branch?       | 4.3
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | none
| License       | MIT
| Doc PR        | not needed

In #31288, we gave the `RoutableMessageBus` a "default" bus. We did that by using the `MessageBusInterface` service in the locator. But, no such service exists - I think that was just a huge oversight (and maybe @dirk39 named a bus this in the project he was testing on?). The services in the locator are very simply the keys under `framework.messenger.buses` or the default, which is a single `messenger.bus.default` id. There is an alias in the container for `MessageBusInterface`, but this is not added to the locator (and adding it would be a bit awkward, as `MessengerPass` is in the component and the interface alias is entirely a framework thing).

Cheers!

Commits
-------

42e0536 Changing how RoutableMessageBus fallback bus works
@fabpot fabpot mentioned this pull request May 22, 2019
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.

3 participants