-
Notifications
You must be signed in to change notification settings - Fork 54
VSCode 1.107 #753
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 1.107 #753
Conversation
1c85ad7 to
8c9c6ba
Compare
Use getWorkerUrl instead of getWorker to let VSCode instantiate the Worker itself, as it already includes the cross original worker logic, and also to homogenize with the extension host worker, which only uses getWorkerUrl
8c9c6ba to
79d5ce4
Compare
onora-hbl
left a comment
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.
LGTM
|
@CGNonofr so now we can override where the extension host worker is loaded from? |
kaisalmen
left a comment
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.
LGTM. Thank you. As usual, I will test this downstream.
Can you explain a bit what you mean? do you mean in the code? or the url? I don't expect it to be more than a refactor 🤔 |
|
There is a default, but you can override it, of course. That is done in one or two example and the mentioned tests. I think I need to adjust the above code. |
|
🎉 This PR is included in version 24.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
No description provided.