The `SimulationScreen` removal in v3 should be marked as a breaking change

[itaranto]

I'm migrating a project from v2 to v3 and I noticed the removal of SimulationScreen in v3.0.6.

This should be documented in CHANGESv3.md as a breaking change.

[gdamore]

Yeah, I guess I should. To be completely honest, the SimulationScreen was mostly intended to facilitate testing, and I didn't consider it as part of our API contract, but I was never clear about that and I think some people built things on top of that I didn't expect. :-)

[itaranto]

To be completely honest, the SimulationScreen was mostly intended to facilitate testing.

Exactly.

My tests break because SimulationScreen is missing. I'm not using SimulationScreen in any weird way, I'm only using it for testing.

[itaranto]

To be completely honest, the SimulationScreen was mostly intended to facilitate testing.

Exactly.

My tests break because SimulationScreen is missing. I'm not using SimulationScreen in any weird way, I'm only using it for testing.

Just to be clear, I'm not asking for SimulationScreen to be added again. I'm just proposing mentioning that as a breaking change as part of the v3 release.