Skip to content
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

Added StandardJS Static Test to Repository #51

Open
wants to merge 5 commits into
base: f24
Choose a base branch
from
Open

Conversation

sschauk
Copy link

@sschauk sschauk commented Oct 22, 2024

### What types of problems are you hoping your tooling will catch? What types of problems does this particular tool catch?
StandardJS is a static analysis tool that checks the code quality in JavaScript applications, making the code more readable and maintainable as it gets more complex and has more contributors. This tool is meant to catch issues in the code that make it less readable in hopes of fixing the syntax and enhancing readability and understandability.

### What types of customization are possible or necessary?
To customize, you can define global variables that could otherwise cause linter errors, ignore certain files or directories, specify the environment so the linter can adapt to it, customize the error output, and do many more things to customize it further. For this case, I chose to customize global variables and ignore directories like node_modules and tests to avoid linting these massive directories and speed up the process. Overall, these customizations are convenient but not necessary.

### How can/should this tool be integrated into a development process?
You should install the style linter with the command npm install standard --global. Then, you want to add the command "standard" to your testing commands in package.json so that you can run npm run static-test to return the result of StandardJS.

### Are there many false positives? False negatives? True positive reports about things you don’t care about?
There are few false positives or false negatives since this tool searches for and analyzes code quality. This means it's a simple process where the tool scans the code and identifies changes to enhance readability and quality.

### Screenshot of test running
Screenshot 2024-10-22 at 4 21 20 PM

@coveralls
Copy link

coveralls commented Oct 22, 2024

Pull Request Test Coverage Report for Build 11486684831

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage decreased (-0.005%) to 82.685%

Files with Coverage Reduction New Missed Lines %
src/meta/errors.js 1 76.74%
Totals Coverage Status
Change from base Build 11467018223: -0.005%
Covered Lines: 22330
Relevant Lines: 25587

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants