Using jsverify
Closed this issue · 5 comments
Is there any specific reason not to use https://github.com/jsverify/jsverify for this?
Because fantasy check was out way, way, way before
https://github.com/puffnfresh/bilby.js/blob/master/src/check.js see original version
@SimonRichardson alright. I did not check that. I suppose switching to jsverify might make sense in the same way that switching from nodeunit to mocha might be a good idea. Of course neither is a defect.
I was just wondering. Thanks for your swift response.
If you want to change then we should change all the repos for consistency.
On Sun, 21 Feb 2016, 11:15 Tobias Pflug notifications@github.com wrote:
@SimonRichardson https://github.com/SimonRichardson alright. I did not
check that. I suppose switching to jsverify might make sense in the same
way that switching from nodeunit to mocha might be a good idea. Of course
neither is a defect.I was just wondering. Thanks for your swift response.
—
Reply to this email directly or view it on GitHub
#9 (comment)
.
Yes, you said that. I think the all or nothing approach means it will always stay the way it is. But I am only an otusider to this as I already pointed out.
Thanks.