itsgoingd / itsgoingd/clockwork
suggestion: possibility to see operations called inside of Laravel defer() helper?
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 6k
- Forks
- 333
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
I noticed operations done inside the defer() helper don't get added to the request data
For example database operations even though successful are not shown
defer(function() {
// this doesn't get logged
Model::create([...]);
});
Laravel Defer Helper documentation
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Clockwork's Laravel request handling around the defer() helper and the database operation shown with Model::create([...]). Check how request data is collected for deferred callbacks, then verify that successful operations executed inside defer() appear in the request data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel, php
- Domain
- devtools, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100