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
Bug: jsx indentation with 'switch' statements #597
Comments
No, this is intentional. Originally when I started building JavaScript beautifiers they were primarily tooled towards the JSLint style guide, because at the time it was the complete and easily testable style guide around for JavaScript. This is what JSLint recommends. I could put an option to indent the |
Thanks for the reply. I have noticed that in js files atom-beautify would actually indent the case by two space from switch. We are currently using jsx and js files together and experiencing eslint conflicts between the two. Can you reconcile them or advice. Thanks |
I can hide the default behavior behind an option. |
yeah, it would be great if you can provide the option. |
+1 for the ability to configure the switch/case indentation behavior in Javascript. |
Waiting on Atom/settings-view support: atom/settings-view#736
it is problem solved? i run into this problem too. |
@calidion Could you create a debug.md file using Atom Beautify and paste that into a gist? It will provide me all the details I need to reproduce the problem. |
Still no possibility to set switch/case indentation in JavaScript (or even better, autoload the SwitchCase setting from .eslintrc) ? |
Does the |
Just realized that the jslint-happy setting was the culprit. Turned it off and the indentation got fixed. However, would still be nice to have possibility to set this directly from .eslintrc, as suggested in #897 . |
This issue has been automatically marked as stale because it has not had recent activity. If this is still an issue, please add a comment. It will be closed if no further activity occurs. Thank you for your contributions. |
@prettydiff ,
The indentations starting from line 3 are not quite right, please look into this.
before:
after:
The text was updated successfully, but these errors were encountered: