You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, and thanks for the input. Yeah, I believe we don't support this. In my view, we don't want to strive to support every niche syntax of CSS, and I don't really see enough of a benefit here. I mean, one could always go with e.g. width-10?
The main reason is I want to use a stripped down version of tailwindcss and one of the features that I want is arbitrary values. I guess there is a way to do something like this without escaping, but that would be a nice little feature in my opinion.
Also thank you for this library 👍
Thanks! I see, at least I understand the use case better. I am open to considering it, especially with a pull request. If it looks simple enough and doesn't slow things down, then it sounds good to me.
I am generally a bit worried that this style of setting properties can lead to a huge number of rules. And I don't know exactly how well the library is optimized for such use cases. Maybe it's okay though, unique classes should be quite fast to lookup. Though, using style properties when one can should generally be preferred.
Hello, I would like to be able to use escaping in RCSS selectors like this
Now square bracket isn't escaped but becomes a part of the selector
The text was updated successfully, but these errors were encountered: