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
I think .editorconfig will potentially have too many conflicts with eslint+prettier and will need to be maintained separately.
If you want to work on this to show an example of what the config will look like, I'm happy to take a look, but do note, we don't want editorconfig conflicting with eslint/prettier.
Install the eslint-config-prettier package from NPM,
npm install eslint-config-prettier --save-dev
This package disabled all ESLint rules that overlap with Prettier, so to enable the prettier rules, add "prettier" to the end of the extends array inside .eslintrc.js file...
extends: ['airbnb-base', 'prettier'],
Now, we should be all good! Prettier should work together with ESLint to enforce coding standards and formatting rules at the same time.
and
While Prettier mostly takes care of code formatting, EditorConfig can enforce additional restrictions on a developer's editor. In some cases, Prettier can also use EditorConfig configurations to auto-format our code as well if, (1) .prettierrc file is not provided and (2) the Prettier VSCode extension is already installed.
This is my first foray into a typescript project, but there seems to be some compatibility with some config
Here's another post that seems to cover a lot of the same setup
Describe the problem
I would like to have a
.editorconfig
file as to the recommendation from: https://editorconfig.org/This is needed since not everyone will be using vscode
Describe the proposed solution
I would like to see a
.editorconfig
file in the form of, updated to the needs of this project:Have you checked if this issue has already been raised?
Code of Conduct
The text was updated successfully, but these errors were encountered: