-
Notifications
You must be signed in to change notification settings - Fork 5
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
Extension incorrectly patches VSCode 1.95.x and breaks application #8
Comments
Have you ever start VSCode without any other extension? I have tested on Windows and MacOS, and everything works. You can see the reproduction in #2 |
off topic but could you share how you got the vertical sidebar tabs in the screenshot above? |
@subframe7536 It appeared that application cache of VSCode caused this to happen. I'm not sure which cache caused it but it was either by the data in the Might be good to include this in a FAQ somewhere. If you think no further action is needed, you can close this issue. @Aworldc |
I don't experience any broken styles, but the styles from my overrides are not applied either. VSCode still warns me though that "Your Code installation appears to be corrupt.", which is expected. Still, no style changes are applied, even when I see this in Output. I am on
|
Thanks for your feedback. There is already have a FAQ in README: https://github.com/subframe7536/vscode-custom-ui-style?tab=readme-ov-file#faq BTW, I stick my VSCode version to 1.94.2. There is a performance issue which cause high cpu usage in 1.95, and the reload button the longer instantly effect since it's resource load strategy changed. |
The extension incorrectly parses VSCode application data, causing it to break the installation. Tested on 95.0, .1 and .2, as well as multiple extension versions to rule out the problem.
I've also tested with not setting any customization options, just applying/reloading/patching with no data breaks as well.
Strings look all messed up, and the whole functionality of VSCode seems broken.
The text was updated successfully, but these errors were encountered: