This is an interesting idea!

This also seems to be a step in the right direction for maybe having this object be in the draw tree (rather than all of the parts individually).

We should also put aremove method on it that calls down to all of its children.

Yes, we could extend this to something like an ArtistContainer, which itself can support (parts of) the Artist API. But let's start small.

I just realized that we haveContainer, which could be a complimentary approach. However, I think that a data class is the more simple and understandable approach (-> public concept). Also, I'm not sure we want to buy into the additional functionality ofContainer right now. And finally, the data class and an equivalent Container are API compatible for relevant operations (read-only attribute access). So I don't think adding the dataclass now would render us in an unwanted corner. We could switch to Container later.

Put to draft to rethink this approach vs. Container. Feedback welcome.