Are there going to be setter APIs?

I love the new features, super excited to see them finally being released to the public, so the problem I could think of atm is simply this: when people started creating uncountable numbers of variants(main components), say that you roll out a new feature to solve the repetitive problem later on, how are people going to shrink their library down, by then, without making all already-instantiated instances wild pointers?

Let’s say when you need:
❖ An interactive mutually exclusive radio group with 3 items
❖ An interactive mutually exclusive radio group with 4 items
❖ An interactive mutually exclusive radio group with 5 items
❖ An interactive mutually exclusive radio group with 6 items
❖ An interactive mutually exclusive radio group with 7 items
❖ An interactive mutually exclusive radio group with 8 items
❖ An interactive mutually exclusive radio group with 9 items

❖ An interactive vertical mutually exclusive radio group with 3 items
❖ An interactive vertical mutually exclusive radio group with 4 items
❖ An interactive vertical mutually exclusive radio group with 5 items
❖ An interactive vertical mutually exclusive radio group with 6 items
❖ An interactive vertical mutually exclusive radio group with 7 items
❖ An interactive vertical mutually exclusive radio group with 8 items
❖ An interactive vertical mutually exclusive radio group with 9 items

without having to create hundreds of thousands of mostly identical variants + identical interactions on each variant (with the destination being the only difference)

Ahh just saw your other post in feedback. Might be good to link to it here.

Yes, thank you, Josh ❤️ @Josh I will do that

For more context, please see my → feedback post here ←