@flyboarder oh, hmmm

i feel like :class is becoming less and less useful (or rather, requiring more and more boilerplate) as my app gets more complex and i break components down into smaller pieces

so maybe this is more of a feature request than a bug

is it right to say that if we implement a multimethod that matches every namespace for :class then you would no longer be able to BYO your own implementation?

and also, could we implement something that dispatches on :hoplon.bar/class and :hoplon.foo/class?

@thedavidmeister we could implement something that catches namespaces for class, I believe that would require keyword inheritance, another option is a new macro for the do! multimethod defattribute perhaps?

could you give an example of what that would look like?

Yep, one minute, I'm on mobile right now

or even :class/foo and :class/bar maybe?

i don't know what would be more conventional

@thedavidmeister there are namespaced defaults for :html/* :css/* :attr/* :prop/* :svg/*

yes, so could class be one?

yep

I’ll add one for the :class/* set since this seems useful

nice, ping me when you do and i'll update the test for it

on an unrelated note, has anyone done anything like https://joshwcomeau.github.io/react-flip-move/examples/#/?_k=kmex6e with hoplon?

Not sure, could probably be wrapped tho

Also test passing again

i'll check out the tests

for the flip move thing i was thinking more about the technique than the library, as it seems to be for react

i think rearranging things is a weak point of hoplon atm, so it would be good to see what might be done there

@flyboarder class looks cool 🙂 i added a couple more tests, but it's all passing afaics

could you push to clojars?

@flyboarder @thedavidmeister this is awesome (the class stuff)

@thedavidmeister ill get around to pushing today