Skip to content
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

[Bug] it's remembering variables from all times, from other files #80

Open
lucianahanan opened this issue Sep 29, 2022 · 2 comments
Open
Assignees
Labels
breaking-change bug Something isn't working
Milestone

Comments

@lucianahanan
Copy link

image

image

I tend to use the same variable names on many CSS files. It happens that when I type --, your extension shows a huge list of variables with the same name, and different colors, one for each time I used that variable in a CSS file, with like 50s --text, 50s --heading, 50s --primary.....

The worse is that it's getting hard to find the current variable on the current CSS file, that is the one I'm supposed to call. But there are so many with different colors!

I'm not sure if there is an option to forget other files ever used variables, but well, it's hard to work like the way it is now!

Please help!

@lucianahanan lucianahanan added the bug Something isn't working label Sep 29, 2022
@phoenisx
Copy link
Contributor

phoenisx commented Sep 30, 2022

I am not sure how are you using this extension, because having 50 duplicates for a CSS variable is very less likely in a project.

Have you tried setting up a Multi Root Workspace, an example for the same is present in this repo as well, do check it out, might be helpful for you?

Anyways, I have plans to reduce the number of duplicates in a future release, will take up this task then 👍🏽

@lucianahanan
Copy link
Author

To reproduce the issue, just make a few css files using the same variable, with different colors. Then you will see it. If you create 3 times, there will be 3 variables with the same name, one for each color, in the dropdown list.

@phoenisx phoenisx added this to the 2.6.0 milestone Oct 17, 2022
@phoenisx phoenisx mentioned this issue Nov 1, 2022
8 tasks
@phoenisx phoenisx modified the milestones: 2.6.0, v3.0 Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants