Standardize Error Responses about laravel-api-tool-kit

[iamnomana]

Okay that's understandable. Thank you brother.

…

On Wed, Aug 30, 2023 at 1:45 PM Ahmed Esa ***@***.***> wrote: It seems you are talking about query exceptions , The reason behind this behavior is that showing detailed query exceptions in the error response in production could pose a security risk, as it might reveal sensitive information about your database structure. To avoid this, query exceptions are not directly shown to users in production. Instead, you can find these errors in the log files. While it's possible to customize the way query exceptions are handled and returned, it's generally not recommended due to the security implications. — Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKTCW6ZVUHSOQ34KWWOCUH3XX47Y5ANCNFSM6AAAAAA4EJF5SY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ahmedesa]

It seems you are talking about query exceptions , The reason behind this behavior is that showing detailed query exceptions in the error response in production could pose a security risk, as it might reveal sensitive information about your database structure. To avoid this, query exceptions are not directly shown to users in production. Instead, you can find these errors in the log files. While it's possible to customize the way query exceptions are handled and returned, it's generally not recommended due to the security implications.