Just took a quick look - thanks for starting this :). There’s one if problem immediately - it looks like this is a few weeks out of date, and s lot has happened in the past few weeks. Check out the master branch of the code - it’s quite different. Sorry about that!

Thanks all for the review.
I have an error/home/travis/build/symfony/symfony-docs/components/messenger/transports.rst:: WARNING: document isn't included in any toctree
Help please, how to fix it? What does toctree mean?

Just took a quick look - thanks for starting this :). There’s one if problem immediately - it looks like this is a few weeks out of date, and s lot has happened in the past few weeks. Check out the master branch of the code - it’s quite different. Sorry about that!

Could you please help me with that? which major parts are changed?

@weaverryan can you please check if this PR is still relevant, compared against the current state of the messenger docs?

Thank you

I think due to the many changes in this component since this PR was opened (sorry!) and the fact that I think this is a more advanced thing where looking at the core classes themselves is probably the best way to navigate it, I think we should close this. The only missing thing would probably be something in the mainmessenger.rst documentation that mentions how to "wire in" a custom transport (e.g.TransportFactoryInterface autoconfiguration ormessenger.transport_factory tag).

We're closing this pull request for the reasons given by Ryan in the previous message.@llaakkkk I'm really sorry about this. I hate it when "external changes" force us to close some pull request because the proposed changes are no longer required or for any other reason. Luckily this doesn't happen often ... but sometimes does happen, like this time 😢 I hope this doesn't discourage you from making future contributions. We'll be happy to merge them! Thanks.