UselessCallOnNotNull: fix false positive for unresolved types#4880
Merged
schalkms merged 1 commit intodetekt:mainfrom Jun 1, 2022
dzirbel:listOfNotNullUnknownType
Merged
UselessCallOnNotNull: fix false positive for unresolved types#4880schalkms merged 1 commit intodetekt:mainfrom dzirbel:listOfNotNullUnknownType
schalkms merged 1 commit intodetekt:mainfrom
dzirbel:listOfNotNullUnknownType
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4880 +/- ##
=========================================
Coverage 84.81% 84.82%
- Complexity 3463 3467 +4
=========================================
Files 493 493
Lines 11355 11359 +4
Branches 2090 2092 +2
=========================================
+ Hits 9631 9635 +4
- Misses 674 675 +1
+ Partials 1050 1049 -1
Continue to review full report at Codecov.
|
Fix an issue where UselessCallOnNotNull would report issues when some of the argument types resolved as ErrorType. While it correctly handles cases where the BindingContext cannot resolve a type (the first test case), in cases where a call is made on an unknown type (the second test case, e.g. via takeIf{}) the BindingContext will report it as an ErrorType. Since ErrorType.isNullable() apparently returns false we need to make an exception to ensure the rule behaves as expected.
BraisGabin
approved these changes
Jun 1, 2022
cortinico
approved these changes
Jun 1, 2022
schalkms
approved these changes
Jun 1, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Fix an issue where UselessCallOnNotNull would report issues when some of the argument types resolved as ErrorType. While it correctly handles cases where the BindingContext cannot resolve a type (the first test case), in cases where a call is made on an unknown type (the second test case, e.g. via takeIf{}) the BindingContext will report it as an ErrorType. Since ErrorType.isNullable() apparently returns false we need to make an exception to ensure the rule behaves as expected.