It is awkward to use classes containing numbers

[JohnDowson]

Notably Bootstrap has alot of classes like mx-4, px-3, gy-2.

[lambda-fairy]

Hi @JohnDowson, thanks for the suggestion and PR!

My primary concern with this (and the reason why numbers weren't permitted originally) is that in Rust proper, 0000069 and 69 are considered to be the same number. But if we allow your proposal, then Maud will introduce a distinction between the two. I'm unsure what implications this might have.

In particular:

1. Does Rust itself guarantee that number literal tokens are passed through unchanged to proc macros? (So that the token 0000069 is not normalized to 69 or anything else.)
2. What about other tools, like IDEs or code formatters?
3. Finally, from a user's point of view, would they be confused by this?

Also, consider that there is already an alternative syntax (."mx-4"). See #267.

[puetzp]

For me this is more of a documentation issue than a matter of usability. However since I hit this problem myself and found this issue to resolve it, the documentation was updated and explains how to use the "alternative syntax" in order to use numbers in class names.
From my point of view the docs are fine now and there is no need to spend (probably) a lot of time to evaluate the implications mentioned above.

[trepidacious]

I ran into a similar issue with tailwind, so far my preferred approach is to just use class="some-class" or class=(splice). I don't think this is mentioned in the docs but seems to work fine? One thing I did notice is that if I use .class1 .{(splice)} I will get both class1 and the spliced classes in the resulting html, using class="class1" class=(splice) seems to miss out class1?

This way I don't need to think about quoting only the class names that need it. Another advantage is that the vs code tailwind plugin just needs rust files to be added to the list of relevant languages and it will then pick up the class names. If I use the .class-name syntax the plugin needs an experiment regex setting to find class names, and it's pretty tricky to find a regex that covers all the options for Maud classes without also picking up false positives on method calls in normal rust code. Finally it makes the class names a little easier to pick out since they're highlighted as strings.

It's a shame because I do think it's cool to be able to have .class-name, especially where there are only one or two classes.