Add capacity to pass bound variables for attribute map

[Sleepful]

In short, previously it was possible to pass an attribute map only by using the map literal, such as:

• ($ my-component {:class "this-is-literal"})

this changes makes it such that the map can be passed as a variable, basically

• ($ my-component [my-attribute-map-variable])

You will notice that I am wrapping the attribute map in a vector in order to hint the macro that the value is bound at runtime.

To understand this change better, please look at:

1. README
2. test/vitest/basic_component.cljc
   a. The (render #($ label-with-attrs [attrs] title input) line shows the usage, rather contrived.

[roman01la]

I don’t like the vector syntax. Instead it should be possible to just provide props as usual and interpret them at runtime, this is how it’s done in all react wrappers

[Sleepful]

UPDATE: I think I found a solution following the idea at the end of this comment, will push update soon.

---

@roman01la I don't like the vector that much either. How could that be done?

Right now the issue is that during compilation time, the bound attributes are indistinguishable from child nodes. Additionally, the child nodes are wrapped in a callback function. This means that at runtime, I have not found a way to differentiate between a bound attribute map and a child node.

Do you see the problem that I see?

wrap-children is the function that turns the args into a callback:

solid-cljs/src/solid/core.clj

Line 47 in 6300922

(defn- wrap-children [children]

Perhaps an idea would be to leave the child-wrapping for runtime instead of compilation, that way the value type can be checked at runtime for something that indicates whether an attribute map is currently being passed. But I dunno, there might be better ways. What do you think?

[Sleepful]

@roman01la updated :) LMK your thoughts!