Token color customizations do not work properly about vsc-material-theme HOT 6 CLOSED

Just remove the "Community " from "[Community Material Theme Darker High Contrast]".

Also make sure to disable semantic color highlight to replicate old syntax colorization, but we don't recommend it. If you want to keep vscode semantic highlight on (default) you may need to update the selectors. You can read more here #1274

from vsc-material-theme.

We deprecated Community Material Theme in 2020, and the last visual update was in 2016. We offered many years to migrate actually. We just removed it from the marketplace now.

Make a migration guide for settings

There is, based on whether you use semantic highlight or not. Adapt your settings accordingly. But consider code scopes are changed a lot since 2016, so you may need to run scope inspector again to check the names (they also change based if semantic highlight feature is on or off)

Should work the same. Otherwise, there should be a migration guide for settings.

Go to vscode repository and report the issue to them, since semantic highlight is a vscode feature.

Make a migration guide for settings
OR explain that settings are different and show where to find out. This will still waste people's time but at least it's better than having to make an issue on GitHub to find out.

We don't want to replicate vscode documentation, you were just using an obsolete theme stuck in 2016 and never supported semantic highlight and new scopes released in 2020. What you think was a correct highlight was just missing highlight or global scope usage.

Your options

If you like to learn how Vscode has worked with semantic highlight since 2020, we encourage you to read their documentation about semantic highlight. Everyone should know the tools they're using.

• You can still use the legacy version which doesn't support semantic highlight
• You can just use the new theme with semantic highlight on, and enjoy the advanced code highlighting.
• You can use the "new" theme with semantic highlight off (check "With semantic highlight OFF" section), and customize what you don't like.

That's everything you should know and all the possibilities. There are no limitations.

from vsc-material-theme.

I appreciate the quick answer, but the whole point of the issue is that changing the settings I have to the 'new' theme does not change the highlighting in the same way.

Just remove the "Community " from "[Community Material Theme Darker High Contrast]".

What you state is not helpful, this is what I did, and the syntax still looks different. Did you even read the issue closely? Perhaps you did, but you didn't try to replicate it because you would be able to tell that the colours are different. The whole point of why I made the issue

See the parenthesis in 'To Reproduce' step 1.

Also, I point out that there should be a migration guide since the community extension was deprecated in favour of this extension. Sure, there might be differences, but then there should be a migration guide, as I've also stated in the original issue.

What I'm experiencing is not changing the theme name. A clear indicator of this can be seen in the before/after screenshots. The before has Purple for types, which is also somewhat present in the after.

But look at the keyword Parse and tell me if you can see a difference. There is, which shows there's a difference in how the settings work. So, to say it again, there should be a migration guide and not a discussion on Github that does not explain the differences between the deprecated extension and this one which we're now supposed to use; and is not easily searchable. It should be stated on the extension READMEs. I rarely use Github, I guess others migrating also don't - it's fairly common sense to write the information on the extensions themselves

Just to reiterate 'just' make a migration guide. At least write somewhere that people migrating would have to change their settings. But to go all-in would be to explain the differences since there are differences.

I know I repeat myself a lot here. But I hope you realise the points I'm trying to make:

• Make a migration guide for settings
• OR explain that settings are different and show where to find out. This will still waste people's time but at least it's better than having to make an issue on GitHub to find out.

Deprecating an extension for another one that introduces changes should come with a warning, guide (if needed), or at least a statement saying there are differences.

And btw, the issue you linked is not helpful, it does not describe the few changes I have and what they should be going from deprecated to the new extension. I want some explanation of the differences, I didn't choose to deprecate the community extension; people working on the two extensions did. It's not on me, the user, to figure these things out.

from vsc-material-theme.

I could edit my comment but it's already a wall of text. Sorry for the double notification:

I know I'm not the only one not using GitHub regularly. I dislike using discussions to convey changes of this magnitude. Discussions are used for mostly user-to-user interactions, where maintainers/owners can chime in. It shouldn't be a place to tell about deprecations or how to customize a plugin for a text editor.

from vsc-material-theme.

Thank you for the comprehensive answer.

The Discussions page is still not the correct place for the information. There's a wiki, and you have a README that should at least direct users to the relevant topics on the discussions page if you insist on using it for the wrong purpose.

GitHub Discussions is a collaborative communication forum for the community around an open source or internal project. Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike GitHub Issues. Discussions enable fluid, open conversation in a public forum.

https://docs.github.com/en/discussions/quickstart#introduction

As a UX designer, I expect that you understand the problems with the experience I, as the user, have. The extension wasn't listed as deprecated before December 1st. How am I to know that I use an obsolete extension when it's there and it doesn't say so anywhere?

I want to thank you for all the work on Material Theme. I love the whole design system and am happy it is integrated into my work environment. I'm mostly talking about the experience, and I am trying to convey how it is confusing and a waste of time to go through all of this when it could have been easily prevented by readily available information.

I'm looking forward to using the new features, and will of course spend the time necessary to utilise the new systems VSCode has. It sounds like a lot of fun to get it all set up how I'd like it. Thanks again for the hard work. I hope people migrating will be able to see these links in the README or described in a wiki, where this kind of information belongs; which is not me being pedantic, it's agreed upon ways of doing things. Having all this info in discussions is not good UX, and I expect more from the Material Theme team.

Have a great Christmas!

from vsc-material-theme.

The extension wasn't listed as deprecated before December 1st. How am I to know that I use an obsolete extension when it's there and it doesn't say so anywhere?

There was a big deprecation statement at the top of the readme since 2020.

by readily available information.

Which are in our discussions 🥲

Have a nice day.

from vsc-material-theme.