Open tony1ee opened 2 weeks ago
@ExperimentsInHonesty are you interested in making use of a JS style guide in some manner?
Regarding linters - I want to mention that there was some work done on ESLint and eslint:prettier
You'll note that some of the above are still draft PRs. I believe there are several reasons why the work did not progress:
// eslint-disable-next-line
which ignores the rules for the next line of code, or // eslint-disable-line
, which ignores the rules for the current lineSuper-linter
was used. While Super-linter
supports CSS and ESLint, it did not have a spell checker that was compatible with the Code Spell Checker for VS Code. So we might want to consider Mega-linter
. @ExperimentsInHonesty are you interested in restarting the discussion around ESLint and prettier?
@roslynwythe @tony1ee
@ExperimentsInHonesty are you interested in restarting the discussion around ESLint and prettier?
After all the spelling issues are addressed.
For future discussion: Since we are talking about linters, here are comments regarding the lint-scss.yml
workflow and the github/super-linter
Dependency
4349
Emergent Requirement - Problem
As our project grow and attract contributions from a diverse group of developers, we have different styles of coding styles across our codebase (trailing spaces, spaces between operators, braces style, etc.). This poses a challenge for readability, maintainability and collaboration.
Proposing we explore the feasibility of adopting a unified coding format standard.
Issue you discovered this emergent requirement in
6777
Date discovered
05/01/2024
Did you have to do something temporarily
Who was involved
@tony1ee @gaylem
What happens if this is not addressed
Resources
Why Prettier Firefox CSS Guidelines VS Code Formatter: TypeScript Airbnb JavaScript Style Guide Google JavaScript Style Guide
Recommended Action Items
Potential solutions [draft]
We can solve this in several steps: