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] proposed mappedEditProviders API evolution with 1.94.X #14268

Open
Tracked by #14266
rschnekenbu opened this issue Oct 8, 2024 · 0 comments · May be fixed by #14276
Open
Tracked by #14266

[vscode] proposed mappedEditProviders API evolution with 1.94.X #14268

rschnekenbu opened this issue Oct 8, 2024 · 0 comments · May be fixed by #14276
Labels
vscode issues related to VSCode compatibility

Comments

@rschnekenbu
Copy link
Contributor

There has been additions to this proposed API used by Typescript builtin.
This proposed API is currently stubbed in Theia (see #13681). The additional elements shall also be stubbed in order to start latest typescript builtin in theia.

@rschnekenbu rschnekenbu self-assigned this Oct 8, 2024
@rschnekenbu rschnekenbu added the vscode issues related to VSCode compatibility label Oct 8, 2024
@rschnekenbu rschnekenbu removed their assignment Oct 8, 2024
rschnekenbu added a commit to eclipsesource/theia that referenced this issue Oct 9, 2024
…e 1.94

fixes eclipse-theia#14268

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 9, 2024
…e 1.94

fixes eclipse-theia#14268

contributed on behalf of STMicroelectronics

Signed-off-by: Remi Schnekenburger <rschnekenburger@eclipsesource.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
Development

Successfully merging a pull request may close this issue.

1 participant