Several smaller issues in multiple choice data in the backend
Currently, the code that handles multiple choice question checkbox data has multiple bugs.
-
The tableMultipleChoiceOptionstores both aProblemand aFeedbackOption, which in principle allows the database to become inconsistent (when theFeedbackOptionof aMultipleChoiceOptiondoes not belong to the problem of theMultipleChoiceQuestion). The solution is to only refer to theFeedbackOption. -
The pageof aMultipleChoiceOptionshould be the same aspageof aProblemWidgetthat 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