Skip to content

Support for special characters in css class names #103

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

Open
m2de opened this issue Dec 6, 2017 · 3 comments
Open

Support for special characters in css class names #103

m2de opened this issue Dec 6, 2017 · 3 comments

Comments

@m2de
Copy link
Contributor

m2de commented Dec 6, 2017

The plugin currently doesn't work if css class names use special characters (e.g. .foo\:bar or .foo\/bar). There are a couple of different places where this becomes a problem.

  1. Class names with special chars don't appear in the auto-completion dropdown
  2. When a class with a special char is used inside a class="foo:bar", triggering the auto-completion after will no longer display the correct classes in the dropdown.

While unusual, the special characters are supported/valid in CSS so it would be great to also add support here.

@JoshWeb
Copy link

JoshWeb commented Jan 30, 2018

I also have this issue, dashes work okay .block--mod, but underscores don't .block__elem. This is particularly a problem when you use BEM naming convention.

@onetrev
Copy link

onetrev commented Feb 13, 2018

Whoops, I guess the issue I created is a duplicate of this one. I did include a few details to hopefully help the author or someone else develop a fix for this. I linked to another extension that does support special chars, but isn't overall as good as this extension.

@macCesar
Copy link

May I add that it also stop working when using parentheses in class names, for example: text-(1rem)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants