Chore: increase camelcase test coverage #11299
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
eslint-deprecated
bot
added
the
triage
RedTn
force-pushed
the
test/camelcase-increase-coverage
branch
from
b463091
to
711d194
Compare
RedTn
changed the title
g-plane
added
rule
ilyavolodin
approved these changes
Jan 21, 2019
gyandeeps
approved these changes
Jan 21, 2019
not-an-aardvark
added
accepted
not-an-aardvark
approved these changes
Feb 1, 2019
eslint-deprecated
bot
added
the
archived due to age
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[X] Other, please explain:
Increase test coverage
What changes did you make? (Give an overview)
Increase test coverage in lib/rules/camelcase.js by writing test cases that hit missing branches/statements
Is there anything you'd like reviewers to focus on?
Coverage added in this screenshot