Describe the bug
When a module added to the config is removed by the faculty, it is not fully removed by the validation logic
To Reproduce
Steps to reproduce the behavior:
- Run the following in devtools to simulate a deleted module
var timetablesObject = JSON.parse(localStorage.getItem("persist:timetables"));
timetablesObject["lessons"] = '{"2":{"BLABLABLA":{"Sectional Teaching":[17],"Tutorial":[14]}}}';
localStorage.setItem("persist:timetables", JSON.stringify(timetablesObject));
- The module remains in localStorage as
lessons:"{"2":{"BLABLABLA":0}}"
Expected behavior
While there are no user-facing errors, I think a better UX would be to inform the user that one of the module has been removed.
The stub should definitely be removed from the config, though.
Describe the bug
When a module added to the config is removed by the faculty, it is not fully removed by the validation logic
To Reproduce
Steps to reproduce the behavior:
lessons:"{"2":{"BLABLABLA":0}}"Expected behavior
While there are no user-facing errors, I think a better UX would be to inform the user that one of the module has been removed.
The stub should definitely be removed from the config, though.