Skip to content
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

NullableToStringCall: fix false negatives with qualified expression #3198

Merged
merged 1 commit into from
Nov 4, 2020

Conversation

t-kameyama
Copy link
Contributor

Fixes #3196

@codecov
Copy link

codecov bot commented Nov 4, 2020

Codecov Report

Merging #3198 into master will increase coverage by 0.02%.
The diff coverage is 77.77%.

Impacted file tree graph

@@             Coverage Diff              @@
##             master    #3198      +/-   ##
============================================
+ Coverage     79.84%   79.86%   +0.02%     
- Complexity     2610     2615       +5     
============================================
  Files           439      439              
  Lines          7953     7962       +9     
  Branches       1516     1518       +2     
============================================
+ Hits           6350     6359       +9     
  Misses          790      790              
  Partials        813      813              
Impacted Files Coverage Δ Complexity Δ
...turbosch/detekt/rules/bugs/NullableToStringCall.kt 80.00% <77.77%> (+5.80%) 16.00 <8.00> (+5.00)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a738300...dd05bc5. Read the comment docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

False negatives in NullableToStringCall
4 participants