You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As development goes, uniform coding style plays big role in maintenance.
Automated checks on code coverage
Steps to reproduce
Expected Behavior
Having a checkstyle in place so its easy to contribute, local IDE setup doesn't hamper.
Having a .editorconfig in place so IDE automatically formats according to coding style
Tests need to be verified and coverage published (could be as a badge, thinking out loud) Note: Initially we can't fail build if coverage goes beyond X%. Once tests are fixed, will have the check in pipeline
Actual Behavior
Many unoptimized imports
Unit tests doing nothing other than printing
Metadata
NA
Typesense Version: NA
OS: NA
The text was updated successfully, but these errors were encountered:
Description
Steps to reproduce
Expected Behavior
.editorconfig
in place so IDE automatically formats according to coding styleNote: Initially we can't fail build if coverage goes beyond X%. Once tests are fixed, will have the check in pipeline
Actual Behavior
Metadata
NA
Typesense Version: NA
OS: NA
The text was updated successfully, but these errors were encountered: