Cloud-CV / Cloud-CV/Origami

Introduce lint-staged to Origami

Open
#290 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
172
Forks
109
PR merge metrics
No merged PRs in 30d

Description

## Description
Linting makes more sense when run before committing your code. By doing so you can ensure no errors go into the repository and enforce code style. But running a lint process on a whole project is slow and linting results can be irrelevant. Ultimately you only want to lint files that will be committed.
I've setup lint-staged with husky in the past in one of my React App. I found it quite useful when working with a lot of people hence suggesting it here.

## Expected Behavior
No new linting issues

## Actual Behavior
There are no such pre-commit linters

Contributor guide

Open the contributing guide

Research direction

Start by locating the repository’s existing JavaScript lint command and configuration, then review where pre-commit tooling belongs. Set up lint-staged with husky so commits lint only the files being committed, and verify that the pre-commit check introduces no new linting issues.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.