-
Notifications
You must be signed in to change notification settings - Fork 29
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
Enable extension in browser environments #286
Conversation
LGTM |
I will try to fix the not working features this weekend, if I'm not able to do it, I'll clean up the MR to only include the highlighting to not block it to be enabled |
071a351
to
eb19a99
Compare
Got it working, it was the document selector, for some reason in the browser it was not working for enabling the language features, so I changed it to use directly the language id strings. Also clean up the MR and removed the refactoring to have less changes |
Signed-off-by: Afonso Fernandes <21228942+afonsonf@users.noreply.github.com>
eb19a99
to
3cd4d47
Compare
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
Do we have to separately add the browser-version to the VSCode marketplace? |
I don't think so, we can trigger the nightly release and check if the new one works |
Hi, in this PR the extension is enabled for web environments such as vscode.dev and github.dev.
This is done by creating a new entrypoint for the extension where only a subset of the features is enabled, namely:
Changed to use npm compile instead of npm watch in extension debugging because to load changes the instance needs to be reload (does not reload automatically) and compile seems to work better and may solve this: #283 (comment)
References