-
Notifications
You must be signed in to change notification settings - Fork 531
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
adding istanbul ignore for pad2 #229
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with this personally
I am also fine with this, and great find @ryhinchey ! I thought there were times in the past I saw the coverage drop randomly but never looked into it that hard... of course the ideal is to test it, but these are one of those things where rewriting it to expose it enough to test would (imo) break encapsulation we'd want to keep private, and some small branch like this we'll just have to skip. This won't be the first place we skip coverage in the various repos, and I think it's a good reason to. I know that was a lot, but just wanted to provide my reassurance 👍 . I am getting a new machine set up right now and will start chewing through a few things tonight, including getting this landed. |
c7768e1
to
850b969
Compare
850b969
to
38e747e
Compare
Well, the PR just failed due to a falling coverage... so maybe still need to understand better what is happening here |
Apparently there is a limit to the length of the ignore comment, lol |
38e747e
to
c54194c
Compare
Related issue: #228
I'm open to an alternative here. I tried adding
sinon@2.0.0
(the oldest version I could install) so I could write a new test with a mocked date; however, sinon wouldn't install correctly in older versions of node #226.