Allow messageClass to be an interface

[Samox]

It makes it easier to implement an event bus. Our __invoke method uses the Event interface instead of the class itself.

[symfony-bot]

Thanks for your pull request! We love contributions.

However, this repository is what we call a "subtree split": a read-only copy of one directory of the main Symfony repository. It is used by Composer to allow developers to depend on specific Symfony components.

If you want to contribute, you should instead open a pull request on the main repository:

https://github.com/symfony/symfony

Thank you for your contribution!

PS: if you haven't already, please add tests, and beware that bug fixes should be submitted on the lowest maintained branch where they apply; only features should be submitted against the master branch.

[sroze]

@Samox the problem is that, if you do that, your handler will be called for every message that implements this given interface, is it what you expect?

[sroze]

See symfony/symfony#27076

[Samox]

@sroze Yes there is one handler for all the events implementing the same interface in my case.
ArticleCreated implements ArticleEvent
and the invoke method would look like:
__invoke(ArticleEvent $event){
if $event isInstanceOf ArticleCreated dothis
if $event isInstanceOf ArticleUpdated dothat
}

Anyway, this pull-request by itself is useless. It allows the bus to record the handler (I can see it in the debug:messenger), but when an ArticleCreated is passed to the bus.dispatch(), it throws an error saying that no handler was found for this type of message.

Is the issue 27076 going to allow mapping handlers with interfaces ? :D

[sroze]

@Samox can you have a look to this pull-request? symfony/symfony#28271

[Samox]

Cool ! Thanks @sroze