You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that the primary issue is how this extension implements the formatting. The extension uses pre-save transformations, instead of being implemented as a formatter. The pre-save transformations do not communicate the additional FormattingOptions, which is why only the two that are part of the TextEditorOptions work.
I am not sure of the implications or feasibility of converting the extension to be used as a formatter instead of the current pre-save transformations. I am going to look into it some more, but I am not sure if it is possible or how long it would take to make the changes.
Please fill-in this template.
code --disable-extensions
and the issue did NOT present itself.Issue
1.5.82
0.16.4
Root
.editorconfig
FileAre there any other relevant
.editorconfig
files in your project? NoExpected behavior
When issuing a Format Document command, the settings above all translate into FormattingOptions passed to a Language Server in VS Code.
Actual behavior
Only the following settings are passed through:
Additional comments or steps to reproduce
See microsoft/vscode-languageserver-node#795 for additional context.
The text was updated successfully, but these errors were encountered: