generated from hackforla/.github-hackforla-base-repo-template
-
-
Notifications
You must be signed in to change notification settings - Fork 93
Labels
complexity: smallfeature: ESLint Warningsrole: Back Endrole: Front Endsize: 0.5ptCan be done in 2-3 hours or lessCan be done in 2-3 hours or less
Milestone
Description
Overview
To streamline linting remediation across the VRMS codebase, we need a script that outputs a list of files with linting errors. This will help prioritize fixes and track progress, and align work across team members.
Action Items
- Investigate using
npx eslint .
with formatting or flags to output only filenames with lint errors. - Experiment with filtering techniques (e.g., using
--format json
or--quiet
) to extract just the file paths. - Create a reusable script (e.g.,
scripts/list-lint-files.js
or shell script) that outputs a clean list of affected files. - Test output across multiple folders to ensure compatibility and accuracy.
- Include count of files with lint errors.
- Add the script to
package.json
underscripts
for ease of use (e.g.,"lint:files": "node scripts/list-lint-files.js"
).- Paste instructions on how to run script within the resources section of the epic: Epic: Fix linting errors across VRMS codebase #1966
Resources/Instructions
- ESLint CLI Options: https://eslint.org/docs/latest/use/command-line-interface
- For broader compatibility, explore writing a simple Node.js script to parse and display filenames from JSON output.
- This issue is part of the epic: Epic: Fix linting errors across VRMS codebase #1966
Metadata
Metadata
Assignees
Labels
complexity: smallfeature: ESLint Warningsrole: Back Endrole: Front Endsize: 0.5ptCan be done in 2-3 hours or lessCan be done in 2-3 hours or less
Type
Projects
Status
In progress