-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Mailer] Move abstract test case to Tests/ #39530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
5915563
to
3edb830
Compare
src/Symfony/Bundle/FrameworkBundle/Test/MailerAssertionsTrait.php
Outdated
Show resolved
Hide resolved
src/Symfony/Bundle/FrameworkBundle/Test/MailerAssertionsTrait.php
Outdated
Show resolved
Hide resolved
@nicolas-grekas I bumped all in |
That's a BC break, isn't it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a BC break, isn't it?
in theory yes, in practice using this Test
namespace was just a workaround for something that is now fixed by the new line in .github/composer-config.json
I'm 👎 here. We have quite some components offering these abstract test classes to be used outside the Symfony framework. They make testing custom mailer transports easier for everyone. This even was the reason this class was moved in In any case, if this is still approved it is a BC break and can't be done in 4.4 imho. But I believe we should keep this as-is and consider the abstract Notifier test case (related PR) a feature. |
Thanks for the context @wouterj this makes perfect sense! |
(I'm sorry if my comment was a bit blunt. With one approval in already, I was in a bit of a rush to prevent quick merge) |
All fine , thanks 👍 |
This PR
is based on https://github.com/symfony/symfony/pull/39495/files#r544203249
cc @wouterj @nicolas-grekas