Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
| * 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. |
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.
This should go into the ChangeLog of FrameworkBundle, not the DI component.
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.
Ah, you are correct! I was confused by the path of theFrameworkExtension. Is fixed.
nicolas-grekas commentedMar 2, 2018
Thank you@apfelbox. |
We will now also autoconfigure the (required) tag
container.service_locatorfor allServiceLocators.I couldn't find any integration tests for the whole list of autoconfigured core services, so I didn't add any new tests.