Bug
Row-displayed counter player causes form to fail
Issue description
When editing an existing topic with a row displayed counter player, the form does not show and on the console the JavaScript error message 'TypeError: Cannot read properties of undefined (reading 'constraints')' is displayed.
Developer comments
This was caused by missing contraints. The row form for the counter player is rendered but the constraints are not present in the client.. The solution is a different fix for [7562, the causing issue]: row displayed topics are now considered always new. Even if they are not. Strictly speaking, always new means that the counter player is conntected 1-1 only. Here they are also considered always new when they are conntected 0-1. Meaning the row displayed topic can exist without an association.
This becomes clearer if you consider, that row-displayed topics usually are adjuncts to "something bigger" A, which i currently do not have a good name for. But the topic is only an adjunct to A, it might be connected to other topics which it is independent of. I am in need of a good typology of association types. Still there remain doubts as whether the decision to make row-display a property of a topic type, was correct, since it might have been better of on the topic role constraint.
|
Work sessions
Start |
2022-04-09T11:51:05
|
End |
2022-04-09T13:05:17
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.