-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Debug] deprecate the component in favor of ErrorCatcher #32303
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
is DebugClassLoader the only debug utility we need to provide ? |
I think so. At least we don't have any other. |
I have just one concern about discoverability. Is this something we should take care of? |
Aren't we regret this in the future if we create new debug utilities? 😕 Also, having the |
That's still the most pragmatic way to solve the issues that the linked issues describe. |
But that still doesn't solve the problem for existing projects, right? 🤔 Their index.php is still referencing the |
As with any regular deprecations. The issue is different, see linked issues. (Sorry I can't elaborate I'm on mobile and about to be AFK) |
I thought the whole point of creating the ErrorCatcher component was to split the debugging part and the part that is required even without debugging turned on. |
The main point was to improve and split the rendering part actually. Splitting the debug tools wouldn't be of much interest to me. |
@fancyweb we could use the flex command |
Keeping the
Debug
andDebugClassLoader
classes in a standalone component creates a pile of complications that don't have to be. Let's make things simple and move everything to ErrorCatcher.Fix symfony/recipes#619
Fix symfony/skeleton#177