-
Notifications
You must be signed in to change notification settings - Fork 65
Deprecation error handling #2491
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
Conversation
Guite
commented
Jun 10, 2015
Q | A |
---|---|
Bug fix? | yes |
New feature? | no |
BC breaks? | no |
Deprecations? | no |
Tests pass? | yes |
Fixed tickets | - |
Refs tickets | #2486 |
License | MIT |
Doc PR | - |
Changelog updated | no |
Collecting related issues in vendor bundles here: |
I think that some deprecated route information comes from the database ( Example content for the
Example content for the
Whereby the second parameter is deprecated. @cmfcmf How to handle that? |
@cmfcmf and I looked at this during the last hour. We did some minor refactorings in order to do what is possible. |
@craigh http://symfony.com/blog/symfony-2-7-1-released
|
see comment in slack. |
I'm not convinced that the code in Route.php is responsible for the deprecated warnings about I don't know how the I hope that helps! |
Thanks @weaverryan for your explaination. @cmfcmf what do you think? |
Yes @Guite, this probably is it. |
The thing @weaverryan suggested has now been added in #2498. |
THANK YOU @weaverryan for taking the time to help us! (conversation began here) |
Cheers! Happy to be able to help out another library in the ecosystem :) |