Closed RemiWoler closed 9 years ago
:+1:
I've been thinking about doing this for a while. I'll try to get started on it this week and keep you updated.
Well, if you make a new branch we can do some PR's? :)
A new repo will be made to contain just the transport and related tests. This will be under the namespace Accord\MandrillSwiftMailer.
The existing class Accord\MandrillSwiftMailerBundle\SwiftMailer\MandrillTransport will effectively become a proxy for the transport loaded from the new repo. This will ensure BC compatibility for people using the bundle just for the transport class, if there are any.
This update will be released as 1.2.0 when it's done, so I've created the branch 1.2.x-dev.
I'll also annotate the old transport as deprecated
:+1:
The standalone transport can now be found here, it's also registered in Packagist. I've also taken the opportunity to shore up the unit tests.
https://github.com/AccordGroup/MandrillSwiftMailer
I'll create a 1.0.0 release for the library when the 1.2.x-dev branch is ready to be merged back into master.
All done, 1.2.0 released
Good job!
Awesome work! This is much appreciated!
As this seems to be the most complete and maintained library for this functionally, I believe it would be helpful to separate the logic into a framework-agnostic library, which the Symfony2 bundle could depend on. For Symfony2, this will provide the same functionality because of Composer (the bundle can require the lib), while for every other framework the library now becomes available to use, without the (unneeded) Symfony2 wrapping.