…by using the newer stache binding syntax instead of can-value? Specifically, I don’t know what name stache expects for this binding. I have tried the following, none of which seemed to do it:
Thanks for the quick responses. The documentation had given me the impression that the newer syntax was able to completely replace the use of can-value and that can-value shouldn’t at this point be needed. Thanks for the clarification that that’s not the case. I don’t know if maybe it’s worth specifying in the docs which cover the new syntax that can-value is still the only and preferred way to handle radio buttons. I guess it depends on how much time it’s expected that can-value will still have this use case.
To help you avoid having to experiment and clarify, you can put can-value stuff in with {($click)} stuff and it works nicely. Eg, this works correctly and as one would hope…
Just a note, if you use ({$click}) and can-value on the same element, the click happens before can-value gets updated so you will need to use a setTimeout in the click handler for things to behave correctly.