Skip to content
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

[vscode] Support DocumentRangeFormattingEditProvider provideDocumentRangesFormattingEdits #12939

Closed
Tracked by #12943
rschnekenbu opened this issue Sep 26, 2023 · 0 comments · Fixed by #13020
Closed
Tracked by #12943
Assignees
Labels
vscode issues related to VSCode compatibility

Comments

@rschnekenbu
Copy link
Contributor

rschnekenbu commented Sep 26, 2023

New API has been added to DocumentRangeFormattingEditProvider in vscode 1.82.0.

DocumentRangeFormattingEditProvider

See https://code.visualstudio.com/api/references/vscode-api#DocumentRangeFormattingEditProvider
See also https://code.visualstudio.com/updates/v1_82#_support-for-batch-range-formatting

@vince-fugnitto vince-fugnitto added the vscode issues related to VSCode compatibility label Sep 26, 2023
rschnekenbu added a commit to eclipsesource/theia that referenced this issue Oct 12, 2023
…ngeFormattingEditProvider

Fixes eclipse-theia#12939
The full implementation requires a monaco update, which provides also this support from vscode 1.82

Contributed on behalf of STMicroelectronics

Signed-off-by: Remi Schnekenburger <rschnekenburger@eclipsesource.com>
rschnekenbu added a commit to eclipsesource/theia that referenced this issue Oct 12, 2023
…ngeFormattingEditProvider

Fixes eclipse-theia#12939
The full implementation requires a monaco update, which provides also this support from vscode 1.82

Contributed on behalf of STMicroelectronics

Signed-off-by: Remi Schnekenburger <rschnekenburger@eclipsesource.com>
tsmaeder added a commit to tsmaeder/theia that referenced this issue Oct 23, 2023
…heia#12939

Contributed on behalf of STMicroelectronics

Signed-off-by: Thomas Mäder <t.s.maeder@gmail.com>
tsmaeder added a commit that referenced this issue Oct 23, 2023
Fixes #12939

Contributed on behalf of STMicroelectronics

Signed-off-by: Thomas Mäder <t.s.maeder@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
vscode issues related to VSCode compatibility
Projects
None yet
2 participants