-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
[5.5] Mix() won't throw an exception #20603
Conversation
You still have log in there. Remove any reference to logging entirely. Report will take care of that. |
It still throws an uncaught exception earlier in the method. Is this intentional? Also, don't see what this has to do with debug mode even though the title to this PR mentions debug mode. |
@taylorotwell sorry. I miss understood your previous comment. The original use case was to allow At the moment when using I have limited knowledge of how to do good error handling but I am guessing that a custom exception for Mix needs to be made and thrown so that it can optionally be handled by developers as they see fit. If that is the case then I will close this PR and give that a try. |
@adampatterson report() calls the report() method of your Exception Handler. So the exception will still be reported to your logs or Sentry or Bugsnag or whatever else you do in your exception handler's report method. |
I am not 100% confident that I am using
report()
correctly but I am getting what I expected as the outcome.I added
report()
tomix()
. In both cases, Sentry collected an entry, and with debut turned off Loggly also collected an entry.Debug = False
<link rel="stylesheet" href="{{ mix('/static/css/basemissing.css')}}">
Debug = True
<link rel="stylesheet" href="{{ mix('/static/css/basemissing.css')}}">
ref #20376