Issue
Currently, the course sent to the backend and the period that correlates to that is sent to the backend are wrong.
Endpoint
POST: /scheduler
Why is the issue a problem
While the database shows that the sent period correlates to the 5th period of World History, instead, the id should correlate with the first period of World History. This breaks demand calculation.
Reproduction steps
Move a course like World History into the first period.
Check the payload body of the request.
Search the database with the sectionID sent.
sectionID is sometimes wrong inside the correlating period.
Issue Currently, the course sent to the backend and the period that correlates to that is sent to the backend are wrong.
Endpoint
POST: /scheduler
Why is the issue a problem While the database shows that the sent period correlates to the 5th period of World History, instead, the id should correlate with the first period of World History. This breaks demand calculation.
Reproduction steps
Photos: