-
Notifications
You must be signed in to change notification settings - Fork 380
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
Replaced deprecated factory_class and factory_method #767
Conversation
Hey, thanks for this! I think BC with older versions of Symfony is still a concern, so it might be worth preserving until the next major version of this bundle. What are your thoughts @lsmith77 ? |
I am ok bumping the symfony dependency to the oldest release that still gets security updates. |
ping |
I second bumping this minimum Symfony version and fixing the YAML/XML/etc factory definitions. |
@lsmith77 - Security updates are provided until EOL, which currently means that security updates will be provided for 2.3 until May 2017. @rvanlaarhoven Hey are you still around to make this change? If not, would you accept a PR to your remote / Allow one of us to re-raise this PR with the appropriate additions? |
Yep, still around. And would also accept PR's to my fork. |
Actually that might not need to happen anymore! /~https://github.com/blog/2247-improving-collaboration-with-forks 😄 |
@lsmith77 The decision on this was not to drop Symfony 2.3 support in the current 1.x release, correct? Should we set the milestone for this to the 2.x branch where we can drop Symfony 2.3 support. |
@antoligy: 👍 |
Removed the deprecated
factory_class
andfactory_method
service definition options and replaced them with thefactory
option.Should I also still reference the old way for Symfony <2.6 usage?