Todos + New Feature Ideas

[mia1024]

Todos

Infrastructure

• Use Docker/Ansible to allow quick and reproducible production server provision
• Use server cluster for the database and create backups in servers from a different company/a CS department server
• More reliable setup scripts/container for new dev environments
• Send Discord/email notification when there is an error (ideally we can detect whether an error is persistent and only alert about those)

Backend

• Replace the user routes with some shared schema (assigned to: Dan)
• Internal caching for common database methods
• Develop ways to set up more than one server process
  • Publish the academic calendar either as a separate feed or directly into the user calendar feed.
  • Possibly allow the user to opt into having their classes removed on the calendar during holidays and final exam week. Further investigation is needed to determine whether we can do this at 100% accuracy for all the 5Cs, and we should not implement this feature if not (someone can miss their classes if we make a single mistake).

Frontend

• Allow hovering on SelectedList to highlight cards in both minimap and schedule view
• Better error message on update failure
  • Bug fix: do not return blank data if update fails
• Filter by section status and half semesters
• Edge case bug fix: currently, if you set up a local account in one tab and log in in another tab, refreshing the tab with local account will overwrite everything without warning
• Set up basic unit tests
• Search: toggle/filter to exclude classes conflicting with the schedule
• Possible filter optimization: use iterators (the current selected list only displays the first 30 results or so, depending on screen height, so we might be able to defer the evaluation of filter keys to when the user scrolls down). More investigation needed to see if this is a). actually good for performance and b). worth it
• Set up a service worker to cache section data in case of network failure.
  • When this happens, a notification should be sent to the user

New features

Filters

• Negative filters
• Filter groups with arbitrary boolean logic

Link Sharing

• Allow users to get a sharable link to their schedule that their friends can see and optionally import
• Create unique links pointing to each section
  • We can also use this for search engine optimization

Image generation

• Generate images of either arbitrary or a wide-set of predefined resolution
  • Especially useful for users who want to set their schedule as their phone/laptop wallpapers
  • Added benefit of PDF generation for very little extra effort

Historical course search

• Either server-side or client-side, allow search through some/all past semesters for a course number or course name
  • This enables quick access for courses that are only offered once-per-year, for example

Announcement System

• A basic system where we can hard-code a few announcements and the users can permanently dismiss the each announcement.
  • e.g. when the beta switches to root domain, an announcement to say the old one is still available at legacy.hyperschedule.io
  • Probably implemented as a toast to bottom-right corner
  • Each announcement should have an (optional) expiration date, after which it will not be shown even if it's not viewed.

[hlu109]

Feature request: exclusion filter for course search

[mia1024]

@hlu109 I moved the comment you made about schedule height to #203 as it is a bug. As for your feature request, can you be more specific? Are you talking about a negative filter (i.e. only display all classes that do not meet the criteria)?

[hlu109]

Ah yeah, a negative filter is what I meant, so something like “area:!Core” to only show classes that are not core.