Open ngnigel99 opened 2 years ago
This issue is not essential to the scope of our program, so we decided to not validate whether a module can be S/U or not. From an implementation perspective, there is also no way to verify this information from NUSMods API.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
Assuming information from NUSMods is correct, the user can edit a module and 's/u' it without the actual ability to s/u the mod in real life.