Skip to content

removing services_test.yaml from symfony/phpunit-bridge recipe #744

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

Merged
1 commit merged into from
Feb 27, 2020
Merged

removing services_test.yaml from symfony/phpunit-bridge recipe #744

1 commit merged into from
Feb 27, 2020

Conversation

weaverryan
Copy link
Member

Since Symfony 4.1, you can fetch private services from a test using
a special method - creating public aliases is not required anymore.

Q A
License MIT
Doc issue/PR Docs already mention this https://symfony.com/doc/current/testing.html#accessing-the-container

I'm removing this instead of creating a new version of the recipe mostly for simplicity. The only version that would still need this and is NOT EOL is 3.4. This recipe change would only affect people installing phpunit-bridge into 3.4 today - I think it's worth just keeping the one recipe version. But I can split into a newer version if we want.

Cheers!

Since Symfony 4.1, you can fetch private services from a test using
a special method - creating public aliases is not required anymore.
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request passes validation.

Copy link
Member

@nicolas-grekas nicolas-grekas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe move the removed comment next to symfony/symfony-docs#12647?

@ghost ghost merged commit 98f1593 into symfony:master Feb 27, 2020
@weaverryan weaverryan deleted the removing-services-test branch March 26, 2020 02:21
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants