Skip to content

Assert::nullOrStringNotEmpty() with string|null will always evaluate to true #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
luca-rath opened this issue Dec 8, 2020 · 4 comments · Fixed by #109
Closed

Assert::nullOrStringNotEmpty() with string|null will always evaluate to true #33

luca-rath opened this issue Dec 8, 2020 · 4 comments · Fixed by #109

Comments

@luca-rath
Copy link

Hello,

public function foo(?string $bar)
{
    Assert::nullOrStringNotEmpty($bar);
}

The above example leads to the following error:

Call to static method Webmozart\Assert\Mixin::nullOrStringNotEmpty() with string|null will always evaluate to true.

The problem is, that it's totally possible for $bar to be an empty string.
Unfortunately I can't provide a playground example, because Webmozart\Assert can't be used there.

@cs278
Copy link

cs278 commented Jul 19, 2021

I can confirm this with these dependencies:

phpstan/phpstan                             0.12.92            PHPStan - PHP Static Analysis Tooln
phpstan/phpstan-webmozart-assert            0.12.15            PHPStan webmozart/assert extension
webmozart/assert                            1.10.0             Assertions to validate method input/output with nice error messages.

@ondrejmirtes
Copy link
Member

Should be fixed in PHPStan core. Once this is fixed, this starts working automatically as well: https://phpstan.org/r/f23ca7f4-0c82-487a-8858-384e8abad8cd

@luca-rath
Copy link
Author

@herndlm @ondrejmirtes Thank you for fixing this issue! 🙂

@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants