Markus Podar

Works for me ``` 📁 ~/tmp $ composer create-project laravel/laravel test-l12 Creating a "laravel/laravel" project at "./test-l12" Installing laravel/laravel (v12.0.1) - Downloading laravel/laravel (v12.0.1) - Installing laravel/laravel (v12.0.1): Extracting archive...

I've been working with JSON api stuff for years and always required this (I _wanted_ the `assertSame` safety so badly) and almost a decade ago came up with this, which...

It's impossible from the above package README or the monolith to figure out it's capabilities 🤦‍♂️ I _think_ the clue is the attr `show_error_on=test` meaning it immediately prints the error...

@prisis all I can say is: thank you! :-)

Wow, this is such a shitshow. Now this, last week there was also a similar thing -> https://github.com/Roave/SecurityAdvisories/issues/137#issuecomment-2514567737 Granted, I'm not associated with either and the final verdict has not...

The real travesty is that it seems anyone can publish any CVE for any package, without maintainer acknowledgement, but then you need to proof they're not valid etc. Something isn't...

Where did you see the issue with the tests (guess not on Linux or Windows, as those tests are green)?

Probably because `\Illuminate\Database\Eloquent\Builder::find` transparently supports finding multiple models by their primary key - L10 implementation: https://github.com/laravel/framework/blob/67d4d0dd8061227ef21a3ed7a0ad57c18d51861b/src/Illuminate/Database/Eloquent/Builder.php#L436-L450 - L11 has done it fancier, depending on whether an array is provided or...

Closing due to lack of feedback

Wow, it would be super useful to not have this clipping at all. I've so many cases where I see the clipping where I realize my "expected" actually is wrong...