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] The extension creates a lot of notifications, even with notifications disabled #118

Open
ezzatron opened this issue Apr 17, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@ezzatron
Copy link

Describe the bug
Even with notifications disabled for the CSS Var Complete extension, somehow I still get spammed with notifications.

To Reproduce
Steps to reproduce the behavior:

  1. Install the extension
  2. Use it
  3. Notifications accumulate over time during normal usage
  4. Disable notifications
  5. Notifications still keep accumulating

Expected behavior

  1. Disabling notifications should disable notifications.
  2. Internal errors that don't affect usage could produce less notifications.

Screenshots

Typical notifications after using the extension for a while:

Screenshot 2024-04-17 at 14 46 18

Extension notifications are already disabled:

Screenshot 2024-04-17 at 14 46 28

Details (please complete the following information):

  • OS: macOS 14.3.1 (Sonoma)
  • VSCode version 1.88.1
  • Extension version v2.6.4

Additional context
Project is using Next.js with CSS modules, along with Open Props as an NPM dependency. Config for the extension:

  "cssvar.ignore": [
    "**/node_modules/!(open-props)/**",
    "**/node_modules/open-props/!((open-props|normalize).min.css)/**",
  ]
@ezzatron ezzatron added the bug Something isn't working label Apr 17, 2024
@klizter
Copy link

klizter commented Aug 20, 2024

Same her, the Range Error pops up when I save files.

Using CSS Modules

@phoenisx
Copy link
Contributor

Thanks for raising this issue.
In an upcoming release, I will be replacing notifications with console logger.

Can u help me with a repro for Range Error pops up? This seems like a logical issue and I would like to understand the issue better. 🙇🏽

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants