Thanks to visit codestin.com Credit goes to github.com
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ATM, when an exception is thrown, we display only the message. But, much more information can be embedded in the exception class.
It's possible to get theses informations via the profiler > logs > errors > context > expand. It needs 3 click to be able to get them.
I think I would be much more convenient to display all theses information right away on the exception page.
And with a click in the toolbar > context > expand
so the question is: Should I open a PR to ship that in SF? (of course, with a better code and look and feel 😂)
The text was updated successfully, but these errors were encountered:
feature #49620 [ErrorHander] Display exception properties in the HTML…
b0054f6
… error page (lyrixx) This PR was squashed before being merged into the 6.3 branch. Discussion ---------- [ErrorHander] Display exception properties in the HTML error page | Q | A | ------------- | --- | Branch? | 6.3 | Bug fix? | no | New feature? | yes | Deprecations? | no | Tickets | Fix #49613 | License | MIT | Doc PR | ---  --- <details> <summary>Code to reproduce</summary> ```php class MyException extends \Exception { public function __construct() { parent ::__construct('some_message', 0, new MyException2()); } public string $myMessage = 'some_message'; public string $myCode = 'some_code'; private string $privateStuff = 'private_stuff'; } class MyException2 extends \Exception { private string $anotherPrivateStuff = 'another_private_stuff'; } ``` </details> Commits ------- b041d06 [ErrorHander] Display exception properties in the HTML error page
Successfully merging a pull request may close this issue.
Description
ATM, when an exception is thrown, we display only the message.
But, much more information can be embedded in the exception class.
It's possible to get theses informations via the profiler > logs > errors > context > expand.
It needs 3 click to be able to get them.
I think I would be much more convenient to display all theses information right away on the exception page.
Example
Before:
And with a click in the toolbar > context > expand
After:
so the question is: Should I open a PR to ship that in SF? (of course, with a better code and look and feel 😂)
The text was updated successfully, but these errors were encountered: