Closed not-an-aardvark closed 6 years ago
Merging #3 into master will increase coverage by
<.01%
. The diff coverage is100%
.
@@ Coverage Diff @@
## master #3 +/- ##
==========================================
+ Coverage 98.35% 98.36% +<.01%
==========================================
Files 14 14
Lines 182 183 +1
==========================================
+ Hits 179 180 +1
Misses 3 3
Impacted Files | Coverage Δ | |
---|---|---|
tests/lib/rules/no-unused-disable.js | 100% <ø> (ø) |
:arrow_up: |
lib/rules/no-unused-disable.js | 100% <100%> (ø) |
:arrow_up: |
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 c6fb10f...85fa282. Read the comment docs.
Oh, wow, thank you very much!!
And I apology that I have not contributed to ESLint recently. I'll back after eslint-plugin-vue
get steadied.
No problem! eslint-plugin-vue
looks like a useful project.
ESLint 4.4.0 will probably be released today. It includes https://github.com/eslint/eslint/pull/8997, which refactors
RuleContext
to rename some internal properties. Since this plugin relies oncontext.eslint
as a private API, it won't work because that property was renamed tocontext._linter
to clarify that it usually shouldn't be used.Additionally, since ESLint 3.18.0, node type listeners need to be added before traversal starts (because they are indexed beforehand in
node-event-generator
in order to support selectors). Sinceno-unused-disable
adds a listener at runtime, this could cause a false negative if no other active rules added aProgram:exit
listener. For example, no error is reported for the following code:Unfortunately, this wasn't caught with
RuleTester
becauseRuleTester
also adds aProgram:exit
listener. (In general, I thinkRuleTester
doesn't support adding listeners at runtime.)