Bilfeldt

@Sammyjo20 Are you able to replicate this on a plane laravel 10 installation with just this package installed and running parallel testing? The macro is only registered if another one...

@Sammyjo20 thanks for the debugging. So there are two questions that should be addressed first here: 1. Why does the logging cause problems? 2. Why are the macros already registered?...

I must admit I don't get it. I just ran this package with parallel testing in another project without any issues. That the app is booted and terminated again should...

Oh yes it really is. We can setup a videocall on monday if that makes debugging easier? It would be fun to try to elliminate other stuff from you app....

Could it be that your app adds some global log context like the user and then there is a logging happening **before** the users table is created?

You are completelt right, I can see that I completely forgot to release this new awesome feature: https://github.com/bilfeldt/laravel-route-statistics/pull/39#issuecomment-2234295159 Simple require `dev-master` instead of version 3.20 while I write an upgrade...

Released https://github.com/bilfeldt/laravel-route-statistics/releases/tag/v4.0.0

Thanks for the PR @svenbw 👍 Can you help me understand the use case for this? Is it because you want to monitor usage for a route like `GET /posts/{post}`...

I am planning on releasing a new major version of this package with this PR, but due to holidays this will not be for the next 2 weeks.

@flexponsive thanks so much for this PR. This is definitely a nice feature. This is a breaking change because of the below, but that should not stop us from implementing...