formatting with Typos

[MiddleTommy]

I like just code but it can be a real pain sometimes when I am not perfect with the keyboard.
often I do a typo like pulbic instead of public etc... If there are typeos in the code the formatting of new lines, curly braces , etc.. gets all screwed up when I keep typing.
Can this be fixed to ignore typos a bit more and guess better at what it is formatting when code is not perfect. It may be alot to ask but Resharper, Visual AssistX and Code Rush never seemed to have this problem. Yes I am a frequent jumper of productivity add-ins. I stick with one until I get fed up with its qwerks or bugs not being fixed or suspicions of crashing visual studio then move on. I would sure like to stay with JustCode. There are always features I miss from one to the next if you want any ideas.

[Kaloyan]

Hi Tommy,

 Sorry for the late response and the inconvenience caused.

We're doing the formatting of code based on our knowledge of the semantics of the written code. Once you produce a typo we could only guess what those semantics were at that point, so the formatting there is not exactly what you might have expected. The formatting of the code following the typo has the same logic. So that's why you get things screwed up there. We'll give it a thought whether we can improve that for the future. 
As for the ideas, you just keep them coming and we'll see how we can fit them into our product so that it makes your life easier.

Regards,
Kaloyan
the Telerik team