Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Autoconfigure service locator tag #26341

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

Closed
wants to merge 2 commits into from
Closed

Autoconfigure service locator tag #26341

wants to merge 2 commits into from

Conversation

apfelbox
Copy link
Contributor

Q A
Branch? master
Bug fix? no
New feature? yes
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #26187
License MIT
Doc PR

We will now also autoconfigure the (required) tag container.service_locator for all ServiceLocators.

I couldn't find any integration tests for the whole list of autoconfigured core services, so I didn't add any new tests.

@@ -6,6 +6,7 @@ CHANGELOG

* added support for variadics in named arguments
* added PSR-11 `ContainerBagInterface` and its `ContainerBag` implementation to access parameters as-a-service
* The `container.service_locator` tag of `ServiceLocator`s is now autoconfigured.
Copy link
Member

@derrabus derrabus Feb 28, 2018

Choose a reason for hiding this comment

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

This should go into the ChangeLog of FrameworkBundle, not the DI component.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah, you are correct! I was confused by the path of the FrameworkExtension. Is fixed.

@nicolas-grekas
Copy link
Member

Thank you @apfelbox.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants