Skip to content
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

Feature ideas #321

itsgoingd opened this issue May 2, 2019 · 1 comment


None yet
1 participant
Copy link

commented May 2, 2019

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 (future release)

  • queue jobs debugging
  • tests debugging
  • timeline improvements
  • 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)

Under consideration

  • notifications tab to support all kinds of Laravel notifications
  • ability to specify a closure for filtering collected requests
  • add request replay support
  • add support for an on-demand mode where Clockwork is active only when the extension is open itsgoingd/clockwork-chrome#7
  • hide clockwork dev tools tab when not used on the site itsgoingd/clockwork-chrome#68
  • collect (simple) responses #127


Repository owner locked and limited conversation to collaborators May 2, 2019

@itsgoingd itsgoingd pinned this issue May 2, 2019


This comment has been minimized.

Copy link
Owner Author

commented Jul 12, 2019

Shipped in Clockwork 4.0

  • show request date #324
  • make ignored packages for the stack traces configurable #306
  • show Redis commands and times #290
  • collect (json) request bodies #267
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.