-
Notifications
You must be signed in to change notification settings - Fork 76
Symfony 2.8 support #325
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
Symfony 2.8 support #325
Conversation
should we then just try to remove deprecation notices/warnings then ? which will be hard because some dev dependencies relies on deprecated features methods/classes. So upgrading is mandatory. |
"phpunit/php-code-coverage": "@stable", | ||
"sonata-project/doctrine-phpcr-admin-bundle": "~1.1", | ||
"sonata-project/doctrine-phpcr-admin-bundle": "^1.1|^2.0", |
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.
we should not allow sonata admin 2.0 as per #325 (comment)
i actually don't mind the deprecations for this branch. i am fine just setting the deprecation helper to not treat them as errors. we need to fix them for the version that supports 3.0 but for 2.8 i would rather have something simple that works with 2.3-2.8 and then we move on with the 3.0 upgrade and don't need workarounds for older symfony versions. |
continuing in #326 |
No description provided.