Skip to content

Adding checkstyle & code coverage verification #36

Open
@snigdhasjg

Description

Description

  1. As development goes, uniform coding style plays big role in maintenance.
  2. Automated checks on code coverage

Steps to reproduce

Expected Behavior

  1. Having a checkstyle in place so its easy to contribute, local IDE setup doesn't hamper.
  2. Having a .editorconfig in place so IDE automatically formats according to coding style
  3. 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

  1. Many unoptimized imports
  2. Unit tests doing nothing other than printing

Metadata

NA

Typesense Version: NA

OS: NA

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions