Skip to content

[12.x] Allow setting the RequestException truncation limit per request #55897

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

Merged
merged 10 commits into from
Jun 6, 2025

Conversation

cosmastech
Copy link
Contributor

@cosmastech cosmastech commented May 31, 2025

Building off of #53734

I saw a comment in the Prism repo mentioning that this would be handy. I think for a lot of client/library code, it would be nice to have this enabled on a per request basis for reporting.

Copy link

Thanks for submitting a PR!

Note that draft PR's are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.

@cosmastech cosmastech force-pushed the dont-truncate-per-request branch 4 times, most recently from 00aa604 to a6f39f3 Compare June 5, 2025 10:36
@cosmastech cosmastech force-pushed the dont-truncate-per-request branch from a6f39f3 to fa3fe2b Compare June 5, 2025 10:37
@cosmastech cosmastech marked this pull request as ready for review June 5, 2025 11:27
@taylorotwell taylorotwell merged commit 2033e4a into laravel:12.x Jun 6, 2025
58 of 59 checks passed
@AhmedAlaa4611
Copy link
Contributor

Should we document something like this? Or, truncateRequestExceptionsAt and dontTruncateRequestExceptions that we have in the Illuminate\Foundation\Configuration\Exceptions is sufficient.

AhmedAlaa4611 referenced this pull request in laravel/docs Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants