Several smaller issues in multiple choice data in the backend
Currently, the code that handles multiple choice question checkbox data has multiple bugs.
-
The tableMultipleChoiceOption
stores both aProblem
and aFeedbackOption
, which in principle allows the database to become inconsistent (when theFeedbackOption
of aMultipleChoiceOption
does not belong to the problem of theMultipleChoiceQuestion
). The solution is to only refer to theFeedbackOption
. -
The page
of aMultipleChoiceOption
should be the same aspage
of aProblemWidget
that should always relate to aProblem
. -
When inserting a multiple choice option via the API by using PUT /mult-choice/<id>
, the id should be optional when the data of a checkbox is first inserted. -
When calling the GET /mult-choice/<id>
, not all data is sent as a response.
Edited by Ghost User