Anybody in favour of using PHP error reporting instead of Kint? |
I find Kint supplies a vast amount of inconsequential data and that PHP default error reporting is far better.
Reason is that PHP stops on the first error, gives the file name and line number which is perfectly adequate. I have modified the following file and prefer this method of Debugging: File: ./system/Debug/Exceptions.php PHP Code: # REACTIVATE PHP DEFAULT ERROR REPORTING
As far as I know that is not Kint. Kint only powers a handful of global functions like `dd()` and `trace()`.
(06-26-2021, 10:42 AM)paulbalandan Wrote: As far as I know that is not Kint. Kint only powers a handful of global functions like `dd()` and `trace()`. I searched for "Kint" in the System folder and found the following references: > 1413 matches across 95 files When CI_DEBUG is activated there is a lot of inconsequential information displayed I find it not easy to trace Bugs. The default PHP exceptionHandlers(), set_error_handler() and register_shutdown_function() all use Kint. I prefer to use PHP default error handling rather than Kint and would like a .env option to deactivate Kint. ./System/ThirdParty/Kint/ ==> 98 items, totalling 415.9 kB
Further improvements to the Original Post #1... modified the following:
File: ./app/Config/Boot/production.php <?php PHP Code: /* The advantage is that both local and online application will raise an error log page and only display errors locally. I think it is far better to log errors raised by the Online Application rather than ignore errors by setting error_reporting(0); |
Welcome Guest, Not a member yet? Register Sign In |