Bug
Select box where always new should be
Issue description
Given an association type which connects a topic type A (a file) to a topic type B, where instances of A can only be a player once (1:1), but for B it is optional and up to 6 (0:6), the form for A shows a select box instead of a always new button to create its unique B.
It also leads to A not being identified as a duplicate, if already present.
Rejection comment
Everything works correctly here. The select is the right input element, because there might be instances of B which do not have the maximum amount (6 in the case above) of As associated. The files are recognized as duplicates. Both behaviors are confirmed with a test.
|
Work sessions3
Start |
2019-11-07T15:52:54
|
End |
2019-11-07T16:19:26
|
Participant |
Robert Cerny
|
Start |
2019-11-08T06:33:19
|
End |
2019-11-08T06:55:07
|
Participant |
Robert Cerny
|
Start |
2019-11-08T07:23:17
|
End |
2019-11-08T07:32:45
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.