nusmodifications / nusmodifications/nusmods
Unable to add certain modules to the Course Planner in Beta version
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 689
- Forks
- 364
- Avg merge
- 7h 5m
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem? Please describe.
While using the Beta version that allows me to plan my modules, I realize that there are some modules that were previously available but no longer exist in NUS mods which could not be added to the planner (e.g. GEC1010, IS1103).
Describe the solution you'd like
It will be nice if modules that were available for a particular year be saved separately in the system to support being added to the module planning system.
Describe alternatives you've considered
Alternative solution will be to allow the user to enter a module freely on their own, while allowing the user to specify what requirement the module fulfil (i.e. science requirement, GE requirement, etc).
Additional context
Screenshot shows that the module does not appear.
Additional suggestions
Might want to look into how different year the requirements of modules are different. For instance, the current GE requirements are as followed:
- GEC: Cultures and Connections
- GEX: Critique and Expression
- GEA: Data Literacy
- GEI: Digital Literacy
- GESS: Singapore Studies
- GEN: Communities and Engagement
Also, I see that currently all data of NUSmods are stored on the browser, and will be lost upon browser cache reset. It will be nice if there is a way to export the NUSmods data and reupload it to restore the configurations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Beta Course Planner's module lookup and the browser-stored NUSmods data. Compare how unavailable historical modules and year-specific requirements should be represented, then define one bounded behavior and its acceptance cases. The issue also proposes free-form modules and data export, so these need separate scope decisions before done can be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, typescript
- Domain
- data, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100