Skip to content

Conversation

@teohhanhui
Copy link
Contributor

Q A
Branch? 1.0 (it's harmless to explicitly declare controller services as public)
Bug fix? no (but it removes deprecation messages since Symfony 3.4)
New feature? no
BC breaks? no
Deprecations? no
Related tickets N/A
License MIT

Services are private by default since Symfony 3.4 (see https://symfony.com/blog/new-in-symfony-3-4-services-are-private-by-default)

Services are private by default since Symfony 3.4
@pamil pamil added Enhancement Minor issues and PRs improving the current solutions (optimizations, typo fixes, etc.). Symfony 4.0 labels Apr 13, 2018
@pamil pamil added this to the 1.0 milestone Apr 13, 2018
@pamil pamil merged commit 7c25299 into Sylius:1.0 Apr 13, 2018
@pamil
Copy link
Contributor

pamil commented Apr 13, 2018

Thank you, Teoh! 🎉

@teohhanhui teohhanhui deleted the fix/controller-services-should-be-public branch April 13, 2018 17:16
pamil added a commit to pamil/Sylius that referenced this pull request May 7, 2019
…s-should-be-public

Make sure controller services are public
pamil added a commit to pamil/Sylius that referenced this pull request May 7, 2019
…s-should-be-public

Make sure controller services are public
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Enhancement Minor issues and PRs improving the current solutions (optimizations, typo fixes, etc.).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants