Thought -- will our API be clearer if we make ArtboardInstance its own type?
For now, there is no separate impl -- though that could change (as we wish).
The real change (pending) would be to change the recent API around passing an "artboard instance" to statemachine and animation instances -- and rather than asserting that the artboard is an instance, we change those signature to be an instance.
I've been thinking about this one too as we reviewed the whole "isInstance field". Seems like just a bad pattern. Separating concerns and complexity (also for code editing) in this way seems really desirable.
Thought -- will our API be clearer if we make ArtboardInstance its own type?
For now, there is no separate impl -- though that could change (as we wish).
The real change (pending) would be to change the recent API around passing an "artboard instance" to statemachine and animation instances -- and rather than asserting that the artboard is an instance, we change those signature to be an instance.
becomes