Add option to turn off On Type formatting

[davidwengier]

Some users want to be in full control of their formatting, and currently achieve this by simply never using the Format Document command. Unfortunately for them, on type formatting still gets in the way.

In the below screenshot the user wants HTML to be at the same level of indentation of any C# block it is in, and manually adjusts as such, but every time they type a close brace on type formatting "fixes" the braces, which ends up breaking formatting for them.

From a video recording: https://msit.microsoftstream.com/video/30b40840-98dc-869c-0048-f1ebd05eceaa?st=65 (should start at 1:05)

The position of the braces in the screenshot is actually correct based on the document as a whole, but the indentation of the <div class="form-group col mb-0"> is one too few, so in context they are incorrect. In the video you can see the braces get indented along with the </ul>.

Note that the user is happy with smart indenting, and wants that to remain active.

[davidwengier]

Updated description and putting this back for triage as I'm not sure this is something we even want to do, let alone with any priority.

[davidwengier]

Blocked on #6212

[ygoe]

Can I tell Visual Studio 2022 that a .cshtml file is not handled by the Razor editor? The situation was bad but bearable in VS 2019. But it has gotten much worse in VS 2022. The new editor is not just slower, it also messes around with my code, indents with spaces instead of tabs where it wants, indents to the first column or other wrong levels as I type, it even deletes parts of the line when I paste in text. Matching bracket highlighting is also a chance game, sometimes it hits, sometimes it misses (preferable backwards when it hits forwards), sometimes it gives up. It's a horrible experience! This makes me wish to open the file with Notepad++ and continue working there. There are so many bugs in the editor that I hardly find the time to report all of them. How could such a pain be released at all? Microsoft is really losing the rest of its reputation in solid UIs and productive development tools here.

[davidwengier]

Thanks for the comment @ygoe. Would it be possible for you to file separate issues for the problems you're seeing, with more information about the before and after state, and exactly what you're doing that causes the problem?

I know there is a "put everything at column 0" issue with TypeScript formatting at the moment, but the team are aware and working on it.

I'm sorry if you think the experience has gotten worse, but if you can provide specifics we are more than willing to investigate and fix issues.

[DamianEdwards]

@ygoe perhaps get a screen recording that captures the various issues you're seeing? I know it can be difficult to isolate to specific feedback items when in situations where it feels like the whole editor is fighting against you.