New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do I keep only the indent rules of prettier or set them to the same effect of prettier using style/indent #387
Comments
I wanted to keep the top style, but now it's the bottom style |
For best results, you should use either prettier or eslint stylistic rules ( For even better results, don't use prettier at all and configure your indent rules like this. |
This is exactly why I'm using this project (antfu/eslint-config) :) All those things you mentioned, you can just get rid of them: rm -f .prettierrc .prettierignore
npm rm eslint-config-prettier eslint-plugin-prettier prettier
# npm rm prettier-plugin-whatever For vscode, just turn off anything prettier and only leave eslint. I don't use vscode so I'm not sure how exactly, but you can probably take inspiration from here (search for |
@thenbe But using style/* does not indent the first effect |
@laterdayi try https://eslint.style/rules/js/indent#flatternaryexpressions and https://eslint.style/rules/js/indent#offsetternaryexpressions |
@Dimava Still can't achieve this effect, can you help me |
|
@laterdayi it should autofix the error on save |
It fixes itself, but it fixes the wrong thing
|
Clear and concise description of the problem
How do I keep only the indent rules of prettier or set them to the same effect of prettier using style/indent
Suggested solution
How do I keep only the indent rules of prettier or set them to the same effect of prettier using style/indent
Alternative
How do I keep only the indent rules of prettier or set them to the same effect of prettier using style/indent
Additional context
How do I keep only the indent rules of prettier or set them to the same effect of prettier using style/indent
Validations
The text was updated successfully, but these errors were encountered: