Feature ideas

[itsgoingd]

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 X-Clockwork-Requested-With header for lean usage clockwork-chrome#7
• hide clockwork dev tools tab when not used on the site Hide Clockwork Tab clockwork-chrome#68
• collect (simple) responses Response Tab #127
• ability to collect applied scopes for eloquent database queries

Rejected

[itsgoingd]

Shipped in Clockwork 4.0

• show request date Is there any way to see Request's datetime? #324
• make ignored packages for the stack traces configurable Make ignored packages for the stack traces configurable #306
• show Redis commands and times Show Redis commands and times #290
• collect (json) request bodies post param not recorded for axios request #267

[itsgoingd]

Shipped in Clockwork 4.1

• queue jobs debugging (Queue jobs debugging #363)
• tests debugging (Added support for debugging tests #360)
• timeline improvements (Extended timeline underground-works/clockwork-app#27)