its

Hey, thanks for another great PR, looks promising. I will try to review and merge it this week.

I ended up reworking this slightly and making it a default, which is a small breaking change for people using the web UI without specifying the paths explicitly.

Hey, thanks for the pull request, but I'm not sure if these need to be configurable. If you want to use Clockwork on a non-default local domain, you can always...

Hey, thanks for your message. This has been a known issue with the default Xdebug configuration. I've finally updated our installation guide, to include this setting - https://underground.works/clockwork/#docs-xdebug-profiler

Hey, I think I forgot to update the iframe when updating the web UI recently, thanks for bringing this into my attention. The web UI is quite broken in master...

The web interface has been updated and old icons cleaned up in master (https://github.com/itsgoingd/clockwork/commit/806cc10b275e791ed6ab6c48ec30a0fcaeea2afb).

Hey, do you have any models defined where primary key is not a string?

Yeah, this is not officially supported by Laravel, but still, we could probably handle this better to avoid the crash, I'll look into it.

Even though this is unsupported use of Eloquent, Clockwork will no longer crash in this case (https://github.com/itsgoingd/clockwork/commit/a59d44f104e199e2298db15a38db73e1d11256fd). To be included in Clockwork 5.3.

It would be cool, if instead of returning `mixed`, we could return the type of the first argument. I wonder if PHPStorm supports the `@template` syntax - https://psalm.dev/docs/annotating_code/templated_annotations/.