clockwork
clockwork copied to clipboard
itsgoingd
Feature ideas
This is an overview of various feature ideas for future Clockwork versions. You are welcome to contribute with your own ideas, please create a new issue describing your idea to do so.
Confirmed (next release)
Accepted (next minor)
- timeline improvements
Accepted (next major)
- ability to specify a closure for filtering collected requests
- add support for search via client ip ("show only my requests")
- add models tab as alternative to database tab more centred around models
- improve handling of large metadata (add hard-caps for the collected data)
- notifications tab to support all kinds of Laravel notifications
Under consideration
- add request replay support
- add support for an on-demand mode where Clockwork is active only when the extension is open https://github.com/itsgoingd/clockwork-chrome/issues/7
- hide clockwork dev tools tab when not used on the site https://github.com/itsgoingd/clockwork-chrome/issues/68
- collect (simple) responses https://github.com/itsgoingd/clockwork/issues/127
- ability to collect applied scopes for eloquent database queries
Rejected
Shipped in Clockwork 4.0
- show request date https://github.com/itsgoingd/clockwork/issues/324
- make ignored packages for the stack traces configurable https://github.com/itsgoingd/clockwork/issues/306
- show Redis commands and times https://github.com/itsgoingd/clockwork/issues/290
- collect (json) request bodies https://github.com/itsgoingd/clockwork/issues/267
Shipped in Clockwork 4.1
- queue jobs debugging (https://github.com/itsgoingd/clockwork/pull/363)
- tests debugging (https://github.com/itsgoingd/clockwork/pull/360)
- timeline improvements (https://github.com/underground-works/clockwork-app/pull/27)