Skip to content

fix: don't report expect(el.innerHTML).toBe(foo) #63

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

Merged
merged 2 commits into from
Jul 9, 2020

Conversation

benmonro
Copy link
Member

@benmonro benmonro commented Jul 9, 2020

What: don't report (or fix) expect(el.innerHTML).toBe(foo)

Why: fixes #61

How: added check for name if value is empty.

Checklist:

  • Documentation
  • Tests
  • Ready to be merged

@codecov
Copy link

codecov bot commented Jul 9, 2020

Codecov Report

Merging #63 into master will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##            master       #63   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines          129       131    +2     
  Branches        18        18           
=========================================
+ Hits           129       131    +2     
Impacted Files Coverage Δ
src/rules/prefer-empty.js 100.00% <100.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 32a5c14...fcaa6a0. Read the comment docs.

@benmonro benmonro merged commit 8497c48 into master Jul 9, 2020
@benmonro benmonro deleted the bug/variable-props-not-empty branch July 9, 2020 21:37
@benmonro
Copy link
Member Author

benmonro commented Jul 9, 2020

🎉 This PR is included in version 3.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

jest-dom/prefer-empty wrong detection, and wrong fix.
1 participant