SOLVED: Points in classes not usable due to "Create multiple global classes at once"

Bugs
1

Hi there,

probably a niches problem, but due to the very good new feature of create multiple global classes at once it’s also not possible to use classes with a dot in them anymore, because they will be splitted… (for tailwind users with arbitrary values like w-[3.5rem] and things like grid-cols-[fit-content(theme(spacing.32))] a bit problematic).

would there perhaps be a way for a user to decide to exclude e.g. the “dot” as a separator?

thanks a lot and keep up the great work!

2

It’s almost like … Tailwind shouldn’t be used in page builders. Yet another reason, since Tailwind breaks conventional CSS rules. Using a period in a selector is bad practice.

3

well, it could be more efficient, but we’re doing quite well with it. much more efficient than leaving the familiar framework for the few times pagebuilder. and as long as @apply is not abolished, it can be maintained quite ok.

but that’s not the topic here… maybe the bricks-team shows mercy :wink:

1 Like
4

Hi,
Thanks so much for your report, and welcome to the forum!

This is indeed a niche report/problem :sweat_smile:
However, Tailwind is no longer a niche product. That’s why we’re trying our best to allow arbitrary values in the future, e.g. by simply removing the prefixed dot - or is there something else against this that I’m not aware of at the moment?

Best regards,
timmse

5

hi timmse,

thank you for the response!

removing the dot as separator would definitely be sufficient.

Just for completeness, other characters that are more often used in tailwind class names (arbitrary values and component classes) are [ ] ( ) - _ / \ ' : and ` ´

thanks a lot!

edit: i forogt the comma, my bad :smiley: (eg. ease-[cubic-bezier(0.95,0.05,0.795,0.035)]).

So “tailwind-safe” would be from the current seperators only “space”

6

thank you very much that this came out directly with the 1.7 final, perfect!

7

You’re welcome!

Unfortunately, the change has created a new bug that will be fixed in the next version:

1 Like