Robustness: even corrupt topicmaps should render partially
One possible topicmap corruption: an assoc is visible while a player is hidden (or not contained in topicmap at all). At the moment (5.0-Beta-4) the Webclient throws
Error: too many add-edges passes and the load spinner goes forever.
Instead the corrupt topicmap parts should be skipped and rendering should continue. The browser console should emit a warning to inform about the corrupt topicmap parts as a means for diagnosis/repair.
Of course the platform should aim for preventing data corruption in the first place.
This is a follow-up of #277