Closed ekkinox closed 5 years ago
+1 to this.
+1
+1
Sigh...
@sroze you might want to install https://probot.github.io/apps/reaction/ to this repository to prevent the above.
While I understand the need to get this functionality asap, spamming people watching the repo with +1 comments is quite annoying.
As far as the solution is concerned, I believe extending configureOptions()
should be the prefered solution? transport_name
could eventually see some use and there should be little harm in adding it as an option, even if it would currently be ignored.
ok, PR available here: https://github.com/sroze/messenger-enqueue-transport/pull/82
Released 0.3.2 with the merged fix.
Since this Symfony's FrameworkBundle PR was merged (4.3.3): https://github.com/symfony/framework-bundle/commit/5205108743c2c9063d88d4362137ca60109adf96
The internal option resolver of https://github.com/sroze/messenger-enqueue-transport/blob/master/QueueInteropTransport.php makes the constructor fail because the key
transport_name
(introduced in commit linked before) is not handled by the option resolver.Error details:
What is the proper approach ?
unset($options['transport_name']);
like done here: https://github.com/symfony/messenger/commit/326990f2c06ec9f3fd3d4b8bb07f9162dff5a520configureOptions()
method to add support of thetransport_name
key (null || string) ?According to your preference, I can PR if needed.
Best regards.