Ticket #418 (new task)
Debug serializer should handle exceptions nicely
|Reported by:||Philip||Owned by:||Philip|
|Priority:||Nice to Have||Milestone:||Backlog|
|Component:||UI & Simulation||Keywords:|
If an exception is thrown (e.g. value outside specified range) while dumping the simulation state with DebugSerializer, the dumping process aborts and returns nothing but an error. That's quite unhelpful when trying to debug errors - it should give as much information as possible (entity id, component type, field name), and continue processing other components, and maybe provide some way to break into a debugger.