Bringing this up again as helix starts looking to approach a more stable version. We've been using our own $ wrapper that supports $ "div.foo.bar"
for a while now, and we're still 😍 for it. Doesn't support ids via #
but that could be fixed I'm sure.
Should I open an issue to track this perhaps?
Couldn't this be a userspace macro?
The app I am working on right now with helix, uses material ui, doesn't even make sense to do this kind of thing, at least I am now aware how it would work.
@ashnur It definitely could stay as one, yup. But I think there's value to having this in core where it's available to everyone by default. It doesn't detract from the material use-case, only acts as a shorter alternative to (d/div {:class "foo bar"})
I know what it is
I know much less about macros 🙂