Fix RiskyTruthyFalsyComparison #94
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gmazzap
approved these changes
Jun 28, 2024
tfrommen
approved these changes
Jun 28, 2024
shvlv
approved these changes
Jul 3, 2024
Chrico
approved these changes
Jul 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
Fixes PSALM alert
RiskyTruthyFalsyComparison.Other information:
FILE: Inpsyde/Helpers/FunctionDocBlock.php
Operand of type list<string>|null contains type list<string>, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead.