-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[DependencyInjection][3.0] Add initialized() to the ContainerInterface #15346
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
Comments
Dropping IntrospectableContainerInterface in 3.0 would mean that it is harder to write code compatible with both 2.8 and 3.0 and wanting to know whether it can introspect the container. |
The issue here is that the interface cannot be deprecated in 2.x, so it would mean it is a removal without deprecation, which is bad for the upgrade. I suggest keeping the interface (with no extra method in it) in 3.x but deprecating it. |
Fine, PR updated. |
…r interface (znerol) This PR was merged into the 3.0-dev branch. Discussion ---------- [DependencyInjection][3.0] Add initialized to container interface | Q | A | ------------- | --- | Bug fix? | no | New feature? | no | BC breaks? | yes | Deprecations? | no | Tests pass? | yes | Fixed tickets | #15346 | License | MIT | Doc PR | - Commits ------- bfddac3 [DependencyInjection] Add initialized() to the ContainerInterface
The
initialized()
method has been added to the container in order to check whether a service is already initialized quite late during Symfony 2 development (#3557). In order to prevent a BC break a new interface was added (IntrospectableContainerInterface
).Let's clean that up in 3.0 and move
initialized()
to theContainerInterface
and dropIntrospectableContainerInterface
.The text was updated successfully, but these errors were encountered: