Markus Staab
Markus Staab
I see now, that you also need the normalized result. its not just a check for compatibility. my suggestion did not fit that.
Macht es vllt sinn dass wir das mit der editor integration verbinden..? Wenn man phpstorm wählt (und ggf. Kann man das künftig im setup wählen?) Werden diese konfigs erzeugt?
thanks for the input. what do you think about turning the assertions into (for all truethy-constant comparisons) ? ```php if ($mixed == 'backend') { assertType("mixed~0|0.0|''|'0'|array{}|false|null", $mixed); } ``` I feel...
and would you be open to do it in small PRs, like e.g. doing "mixed vs. constant-type equal compare narrowing" in a single PR? (or any other small step you...
my thinking is example: `non-falsey-string == int` -> take all candidate [values out of the comparison table](https://www.php.net/manual/en/types.comparisons.php) for the involved types `non-falsey-string` -> `"1"`, `"-1"` , `"php"` `int` -> `1`,...
Looking longer at the comparison table, I think it would be helpful to add a new `non-numeric-string` type. Do you agree?
Ahh just found https://github.com/phpstan/phpstan/issues/10239#issuecomment-1837571316
fixed conflicts
TIL that `'1e-50'` is a numeric string. I guess its super rare, but we might have some logic in the codebase which does not allow `-` in numeric strings.
problem is, we are trying to be defensive and do inspection only for readonly queries (identified by a `SELECT` query type). this can be widened with `RuntimeConfiguration->analyzeWriteQueries()` for more query...