Skip to content

Fix capture_dumps option on laravel dd(); #1762

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 1 commit into from
Mar 21, 2025

Conversation

parallels999
Copy link
Contributor

@parallels999 parallels999 commented Mar 20, 2025

Using laravel dd(); it shows nothing, this fix it,
Apparently there is no way to differentiate dumps from dds, since Laravel's dd first executes a dump(); and then an exit(1);

@barryvdh barryvdh merged commit 7d3b28f into barryvdh:master Mar 21, 2025
27 checks passed
@barryvdh
Copy link
Owner

The default should be false. Can we change that back? See #1782

@parallels999
Copy link
Contributor Author

parallels999 commented Apr 15, 2025

Yes, my bad, I didn't realize that.
But this PR should have fixed #1782
The same thing happened to me, but this is how it was fixed.

@parallels999 parallels999 deleted the collect branch April 15, 2025 22:26
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.

2 participants