vscode-cssvar icon indicating copy to clipboard operation
vscode-cssvar copied to clipboard

[Bug] The extension creates a lot of notifications, even with notifications disabled

Open ezzatron opened this issue 1 year ago • 2 comments

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 avatar Apr 17 '24 04:04 ezzatron

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

Using CSS Modules

klizter avatar Aug 20 '24 21:08 klizter

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. 🙇🏽

phoenisx avatar Sep 24 '24 19:09 phoenisx

Related to the fix made for https://github.com/willofindie/vscode-cssvar/issues/119 I'm moving all notification data into logger.

In case Extension fails or has issues, please report the details from the extension logger. I will improve the logger in the future, once I migrate my code base into a LSP service. For now console logs are the only way to check this extension's logs.

phoenisx avatar Jan 14 '25 07:01 phoenisx