-
Notifications
You must be signed in to change notification settings - Fork 28.9k
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
Unify indentation and formatting APIs #34621
Labels
editor-autoindent
Editor auto indentation issues
under-discussion
Issue is under discussion for relevance, priority, approach
Milestone
Comments
rebornix
added
under-discussion
Issue is under discussion for relevance, priority, approach
and removed
bug
Issue identified by VS Code Team member as probable bug
labels
Sep 19, 2018
This was referenced Nov 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
editor-autoindent
Editor auto indentation issues
under-discussion
Issue is under discussion for relevance, priority, approach
Maybe this is wishful thinking but I am experiencing many subtle issues with the relatively new
editor.autoIndent
feature. It's a very useful one and I want to keep it but it misbehaves quite frequently, see e.g. issues #29390, #32333 and many others. Quite a good example is this (from #32835):Indentation via Format Document:
Formatting via Reindent Lines:
It often seems to me that formatting API produces better results than indentation rules but even if that wasn't always the case it just seems logical to have a single API to power both features. It seems like this to me:
So it's a subset / superset problem and I don't think it should be implemented twice, in a completely different manner. What do you think? Would there be a chance to unify the two APIs and eliminate some bugs along the way?
For reference, some key issues related to this:
The text was updated successfully, but these errors were encountered: