Skip to content

[DoctrineBridge][Routing] Require PSR-11 container instead of Symfony container #21978

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

Conversation

enumag
Copy link
Contributor

@enumag enumag commented Mar 11, 2017

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

The changed classes can easily use PSR-11 container instead of normal symfony container.

I didn't change any classes that have the $container property as protected (for example Symfony\Bundle\FrameworkBundle\Translation\Translator) because I'm unsure whether that would be considered a BC break. Let me know if you want me to change such classes as well.

@nicolas-grekas
Copy link
Member

To me, it should be ok to change even when a protected property is involved: existing code won't break all of a sudden because of the less restrictive type hint. In any doubt, just to it in another PR to have this one merged earlier is this needs to be discussed.

@enumag
Copy link
Contributor Author

enumag commented Mar 11, 2017

Alright, will do it in separate PR.

Also I didn't bother with deprecated classes like ContainerAwareEventDispatcher.

Copy link
Contributor

@GuilhemN GuilhemN left a comment

Choose a reason for hiding this comment

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

👍 but the Routing component is no longer compatible with the DependencyInjection component <3.3 so it's requirements/conflicts should be updating.

@enumag
Copy link
Contributor Author

enumag commented Mar 12, 2017

@GuilhemN Like this?

Copy link
Contributor

@GuilhemN GuilhemN left a comment

Choose a reason for hiding this comment

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

Yes, that's it :+1;

@fabpot
Copy link
Member

fabpot commented Mar 12, 2017

Thank you @enumag.

@fabpot fabpot closed this in 5eae2c7 Mar 12, 2017
fabpot added a commit that referenced this pull request Mar 14, 2017
… instead of Symfony container (enumag)

This PR was merged into the 3.3-dev branch.

Discussion
----------

[FrameworkBundle][TwigBundle] Require PSR-11 container instead of Symfony container

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

As discussed in #21978 here is the second PR.

Commits
-------

857ce7c [FrameworkBundle][TwigBundle] Require PSR-11 container instead of Symfony container
@fabpot fabpot mentioned this pull request May 1, 2017
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.

5 participants