-
-
Notifications
You must be signed in to change notification settings - Fork 36
Tabs vs spaces and single vs double quotes in existing files #118
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
Comments
I don't think this is possible in a reasonable manner. If this would work then as post-processing step after serializing the ast. In that case i think we should rather spend effort in solving the problem once and for all via #100 |
Wouldn't we need to do roughly the same thing in either case? Whether we're using recast or esrap to print the file, I'd expect we would need to tell it whether to use tabs/spaces and single/double quotes. Or does esrap have built-in detection for that already? |
Fair point, looks like you are right. |
Interesting. Maybe we can do the same and see if people complain. If so, then we'll know we need to add an option to esrap |
We now default to tabs and single quotes in new files
We have
guessIndentString
, but it's only used for JSON. Can we useguessIndentString
for JS/TS as well? Barring that, can we set the formatting for existing files to match the default for new files?The text was updated successfully, but these errors were encountered: