-
-
Notifications
You must be signed in to change notification settings - Fork 177
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
Bump monaco version #199
Bump monaco version #199
Conversation
A new enum has been added to the vscode compatibility layer (as vscode-languageserver rely on it). Also the severity enum converter use an internal version of the enum to avoid relying on the vscode module.
Signed-off-by: Roman Nikitenko <rnikiten@redhat.com>
Open in Gitpod - starts a development workspace for this pull request in code review mode and opens it in a browser IDE. |
Signed-off-by: Roman Nikitenko <rnikiten@redhat.com>
a0da73d
to
9269688
Compare
@RomanNikitenko ping me if you have any Qs |
@akosyakov At the moment I have the problems with dependencies.
As result I get errors like: So at the current step I'm looking for correct way to fix this problem. |
@RomanNikitenko we need a new version of vscode-ws-jsonrpc then with 5.0.0. We will have the same issue in Theia. Added you as an admin there: https://github.com/TypeFox/vscode-ws-jsonrpc just ping me when i have to make a new release |
@RomanNikitenko published vscode-ws-jsonrpc@0.2.0, you should be able to use it now |
Signed-off-by: Roman Nikitenko <rnikiten@redhat.com>
@RomanNikitenko Let me know if you need any other support. Usually we will do a dev release from the PR, open a PR for Theia against dev version and test it there. |
@akosyakov I could test it locally first: add for Also for testing it for
|
@RomanNikitenko yes, that's an idea. I will publish it today then?
I will do it for you today. |
I would like to pick up the changes from the PR #191 to have ability to test them as well on dev version for If you don't mind I can merge the changes from the specified PR to my draft PR. |
@RomanNikitenko yes, it is fine |
@akosyakov I think this one for testing goals only and we can streamline the commits when we are ready to merge these changes to master. |
there's going to be Monaco 0.20.x soon 🙈 https://github.com/microsoft/vscode/tree/standalone/0.20.x Should we rather go for it instead? |
Let's stick with 0.19. |
Published dev tag from this branch:
Published 0.19.3 monaco from https://github.com/theia-ide/vscode/tree/standalone/0.19.x
|
@akosyakov I'll apply these versions for |
@RomanNikitenko just open it is as a draft, we can collaborate on it, i.e. i can help writing integration tests while you are fixing others :) more of such we have less work it would be to migrate next time |
It seems we have an issue in the vscode-compatibility (vscode-api.ts): the The consequence is that a DidChangeWorkspaceFoldersNotification is sent at startup, with an identical |
@RomanNikitenko I want to merge it and make a new release. Could you open for a review it please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you @RomanNikitenko
Bump Monaco to 0.19.3
I created the branch based on #198 and tried to fix the compilation errors.