Felix Bernhard
Felix Bernhard
I did some digging and I think I found the cause of the issue. Currently, the type of every **primary key** is determined by Laravel, not Larastan. This happens because...
I don't think the Laravel framework supports/uses `non-negative-int` anywhere in their code. Laravel doesn't parse any schema dumps, so they don't have this information. Additionally, a primary key does not...
Here's a real-world example: ```php $user = auth()->user(); $rule = new \App\Models\Rule(); $rule->user_id = $user->id; ``` ```md > vendor/bin/phpstan analyse --memory-limit=2G Note: Using configuration file C:\xampp\htdocs\bidX\phpstan.neon. 1466/1466 [============================] 100% ------...
> [!NOTE] > I've noticed that this is only reproducible in Firefox, but not in Chrome.
Okay, I will put something together later 👍
Oh, that makes sense. I'm looking forward to a possible workaround!