Add menu builder event for better extendability

[Zales0123]

Hello there! 👋

Recently I've started a new project based on Sylius Stack. So far so good 😄 But, I miss very much the menu builder event that is present in Sylius. It gives much better extendability: for example I can write multiple menu listeners in multiple bounded contexts in my application, not a single one on the high level. Also code looks a little bit simpler 😅

Let me know how it looks for you 🫡

PS. I don't know if there is any BC policy, but I suppose there is not, as it's still pre-alpha version :)

[Prometee]

Good idea to revive this feature.

What about a tagged iterator instead of an event ?

[Zales0123]

Good idea to revive this feature.

🫡

What about a tagged iterator instead of an event ?

I have no preference one over another 🤷 Maybe the only reason to keep it with event is to make it consistent with what is implemented in Sylius - in the end, that was my initial tension, as I expected the menu builder to work the same way in Sylius/Stack as in Sylius/Sylius, but was surprised it doesn't 😅

[loic425]

@Zales0123 You can decorate the service several times for your bounded contexts, return the decorated one when the bounded context decorator does not have the right context. I think that's better than events. Don't you think?