Replies: 4 comments
-
@rconjoe @iAmNsengi @itswael @rconjoe @IGIRANEZAJosue @ZennilGreenherald @siferot @Nicode611 |
Beta Was this translation helpful? Give feedback.
-
I would also consider adding: 'no-implicit-globals': 'error',
'no-undef': 'error',
"no-var": "error",
'no-duplicate-imports': 'error'
'prefer-const': 'error',
'arrow-spacing': ['error', { before: true, after: true }], |
Beta Was this translation helpful? Give feedback.
-
@gbowne1, I agree with the recommendations, and I think it would definitely help maintain quality and consistency |
Beta Was this translation helpful? Give feedback.
-
Yes @IGIRANEZAJosue I agree I'm just against adding lint and prettier rules we havent discussed yet to make sure we are all on the same page. I'm ok with adding whatever rules will follow the style we choose. We can then run lint and prettier as a whole. I don't want too much enforcement because I'm all about developer freedom but not too little either. I did use my local lint rules to lint and prettier during the initial phase. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I was just thinking it might be somewhat helpful to keep things clean pre-commit by adding Prettier and or ESLint and their configuration(s) to the project if so, which and what would the configuration look like?
I do have some ideas..
.eslintrc.js
.prettierrc.js
Beta Was this translation helpful? Give feedback.
All reactions