You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should run a prettier such that code style is consistent, furthermore ideally prettier and eslint are first tried seperately in the ci/cd, and if they fail do not attempt other CI/CD checks, to prevent unnecessary usage.
The text was updated successfully, but these errors were encountered:
SuperVK
changed the title
[Refactor] ESLint fix and enforce
[Refactor] ESLint/prettier fix and enforce
Jun 18, 2024
Talked about this a bit with Samuel, best approach would be to use eslint in a central config, then use either prettier or eslint.style for prettying. Then we can use husky to execute prettier on each commit, and eslint as a first enforce to catch common code smells.
We should run a prettier such that code style is consistent, furthermore ideally prettier and eslint are first tried seperately in the ci/cd, and if they fail do not attempt other CI/CD checks, to prevent unnecessary usage.
The text was updated successfully, but these errors were encountered: