assert VS php-cast

This is not Java where everything is nullable by default. Use that in your favor and set dependencies correctly via constructor like this. For this to correctly work, check the empty_data callable and webmozart/assert package:

I actually do have that case, many of them. For that, I use form_data. This example is a bit old-school, statically analyzed one would be using webmozarts/assert like:

For APIs relying on array and not something like cuyz/valinor (best deserializer I have ever seen), one-liners are still good with webmozart/assert:

// https://github.com/webmozarts/assert Assert::nullOrInteger($price = $data['price'] ?? null); if ($price) { $p->setPrice($price); // we don't care about return value }

as will throw exception immediately, similar to assertion package:

What I do with the VueJS forms is using a assertion library like https://github.com/webmozarts/assert to handle the validation of the incoming data.

Since I've had to work with user-specific data a lot more than usual in the last few months, I've been using assert, webmozart/assert and beberlei/assert, and - since I'm using phpstan - external phpstan rules. But I was never satisfied with Assert::integer($id); to check if $id is actually an int. Mainly because this was only possible in combination with the external phpstan rules that make phpstan believe that $id must now be an int, because otherwise an exception would be thrown. Without these external phpstan rules, $id would still be seen as mixed, for example. My answer to this kind of problem is (for now) php-cast. What do you think? Useless or okay-ish?