0

I'm developing lwc in VSCODE, and today my editor suddenly shows a bunch of SLDS problems just like thisproblems

enter image description here

it is annoying and I do not want to fix it by update the token to a new version or make a custom component... I just want to ignoring the infos by SLDS validation.

ps: adding filters in PROBLEMS do not meet my need, the underline of infos and warnings are still in the editor: enter image description here

3
  • Please note that the old styles were planned for deprecation this release (Summer '21). This change has been postponed, but you should not rely on these styles being usable for much longer. This is like having the Check Engine light on in your car. You're not in immediate trouble, but if you don't fix it soon, you'll definitely be in trouble. – sfdcfox Jun 7 at 7:04
  • @sfdcfox thank you for the information, this change is huge... is there a way to auto fix every token or I have to fix them one-by-one, which will take me pretty much time. – Lanjinest Jun 7 at 7:15
  • We were given a year to make the changes. Presumably salesforce.com knows not everyone made it yet, so we've been given a bit of a grace period. Realistically, all you probably need to do is search your html files for -- and selectively replace them with _ instead. Make sure you review your changes and have a backup, but this is actually a fairly "small" change in most cases. – sfdcfox Jun 7 at 7:20
3

There is a extension installed in VS Code along with Salesforce Extension Pack - SLDS Validator. You should disable it if you don't want any warnings and error highlights related to SLDS in your code markup.

enter image description here

1
  • 1
    Note that this was supposed to be deprecated this release, but was postponed. These are problems that shouldn't be ignored for much longer... – sfdcfox Jun 7 at 7:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.