Add "Too many arguments" message to info
and improve code coverage
#2235
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.
I'm working on some code, and rather than including all my commits in one PR, I'd like to separate a few of the smaller, non-related fixes into their own PR's (for easier review).
Summary
This is a very small change to get the code coverage of the
info
command up to 100%. The currently included versions ofjest
andbabel-jest
still have slightly incorrect coverage reports, but updating them gives100%
on this file. I would like to upgrade all the modules in this repo, but it might make more sense for that to be in a different PR? (I didn't includepackage.json
oryarn.lock
updates in this PR)Test plan
yarn test
__tests__/commands/info.js
has no errorsopen ./coverage/lcov-report/index.html
src/commands/info.js
has improved