Hi @ondrejmirtes

I recently encountered situation where short ternary could be considered useful, for instance when using Datetime::createfromformat. https://www.php.net/manual/en/datetime.createfromformat.php

Since the return type is object|false there is no risk writing

DateTime::createFromFormat(....) ?: $defaultValue

and this is way shorter than

$value = DateTime::createFromFormat(....);
if ($value === false) {
 $value = $defaultValue;
}

But in other cases I do like to forbid short ternary because things like

$intOrFalse ?: $defaultValue

is risky, I might have forgot that 0 will end in the default value.

So if you're interested I see two solutions:

1. Relaxing the "forbid ternary" rules to allow nonFalsey|false conditions (and maybe updating the error message behind the bleeding edge tag)
2. Or introducing a config option to allow nonFalsey|false conditions (maybe you'll have a naming suggestion for this one ?), and when the option is enabled I think the error message should be changed too. (like "Short ternary is not allowed on non boolean falsey type. Use null coalesce operator if applicable or consider using long ternary.")

This is currently a POC which should be updated based on your preferences. :)

Looking at how sometimes some rules are loosen up (like in 8afd4af), I think it could be ok to relax the forbid ternary rule without an option. But your call.

This would also close #268 (Should I assume that since you didn't close the issue, you're open to some suggestion ?)