We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be nice and more secure if we move code in the future if every function would have its own test - ideal in its own test-file.
The text was updated successfully, but these errors were encountered:
🎆 Our test coverage is all green. 🎆
+ Statements : 82.51% ( 453/549 ) + Branches : 81.21% ( 376/463 ) + Functions : 81.93% ( 68/83 ) + Lines : 82.59% ( 446/540 )
PS: There are still two unmerged tests to make it even better.
Sorry, something went wrong.
It would have been better to have these test coverage before the TS rewrite! But better late than never 🤣
Yeah, that's what I plan to do in vis-network. Tests first, TS later.
Thomaash
No branches or pull requests
It would be nice and more secure if we move code in the future if every function would have its own test - ideal in its own test-file.
The text was updated successfully, but these errors were encountered: