Using JS.push we can send arbitrary values (only atoms seem to be converted to string). <div phx-click={JS.push("signal", value: %{...}}> Why can’t we just do that with phx-value? <div phx-click="signal" phx-value={...}>

[image] Sebb: Using JS.push we can send arbitrary values (only atoms seem to be converted to string). I believe the values have to be json-encodable.

phx-value will be encoded as an attribute and therefore will use HTML encoding rules. Via JS it is JSON based.

I understand, that this is the way it is, but I find myself always using JS.push just to not have to convert everything from strings, so I’d like to have the simplicity of phx-value with the power of push/value.

[image] Sebb: so I’d like to have the simplicity of phx-value with the power of push/value. I agree, I see no reason why it couldn’t work this way. It would be a nice addition IMO.

As it is, you’d have to implement Phoenix.HTML.Safe for Map, which would impact things outside of attributes (good or bad). Unsure how painful it would be to alter the heex engine to handle expression attributes in a special way vs other content. The click handler also wont know if you’re trying to…

Why is there no phx-value binding that takes an expression

Questions & Help Questions

trisolaran March 11, 2023, 3:44pm 5

I agree, I see no reason why it couldn’t work this way. It would be a nice addition IMO.