Good question. It kind of depends on what you need in a particular case, doesn’t it? In some cases you have a small, fixed number of things that can be clicked. In other cases you have an arbitrary number of things, perhaps created by the user, that can be clicked. And you have gradations between these two poles. Using Click Int seems awkward and overkill to model the first kind of case.
But if you’re just asking about the second kind of case, dealing with clicks from an arbitrary number of shapes, it depends on how you are modelling your collection of shapes. In a lot of cases List Shape will do, but depending on what the UI is you may have Array Shape or Dict Id Shape or Tree Shape or Zipper Shape, etc. , and this would guide you how structure your Click to index into them.
At least, that’s the way I would think about it. The UI/UX guides your decisions about data structures and how they are updated with Msg types. There’s not a one size fits all approach. That said, your List Shape/Click Int approach is very very common I’d say for basic use cases.
