-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
Coverage #196
Coverage #196
Conversation
I guess I need to wait until #195 may be merged into |
5f3b854
to
b0af281
Compare
1a6661d
to
e70607a
Compare
- Testing: Fix test (was not parsing) - Testing: Fix test (missing an error message)
Also: - internally renames `isCallingBack` to `isCallback` as per file name and usage - removed code block from `always-return` which is not necessary given that "good" return/throw statements cannot occur within shortcut syntax (which expect expressions)
I personally don't care about 100% test coverage, but if we have it, let's try to keep it :D |
Cool--Appreciate the flexibility! FWIW, besides giving some assurances that edge cases have been considered and are working as expected, I find another advantage is ensuring self-documentation for others about what will happen under those edge case conditions. |
What is the purpose of this pull request?
Testing coverage
What changes did you make? (Give an overview)
Builds on #195 (so that there would be a passing tests/linting baseline)
isCallingBack
toisCallback
as per file name and usageIn the process, this PR includes refactoring to remove dead code (and thereby avoid the need for
istanbul ignore
):always-return
which is not necessary given that "good" return/throw statements cannot occur within shortcut syntax (which expect expressions)If you prefer that all of the code be refactored to avoid
istanbul ignore
, I can do so, but I think the other code was more reasonable as a sanity guard (i.e., in case the code were ever refactored, those checks may be necessary).