Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Edit a course from Your Courses with a pencil button

Open
  • Is something wrong?
#291 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Aiden-Trindade is already working on this.

Since Oct 28, 2026.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
43/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
react, typescript
Domain
frontend

Research direction

Start with landing.tsx, FacultySelector.tsx, and the fullCourseData shape; trace how courses are selected, saved, and used to generate timetables. Check the existing slot multi-selector work in #287 and the layout work in #290, and review how faculty priorities are loaded. Done when course edits save at the same list position, cancel cleanly, and regenerate visible timetables while preserving filters.

Written by the indexing model from the issue text.

Description

Scroll down for design

Is your feature request related to a problem? Please describe.

To change a course's slot or faculty, a student deletes it and adds it again. The eye button's popup (#252) only reorders the faculty already picked.

Describe the solution you'd like

A pencil on each course row replaces the eye button and its popup (FacultyPriorityModal). Pressing it puts the selection box into edit mode for that course:

  • Domain, Subject and Slot are filled in, with all of the course's slots selected. Lab-only courses get their morning or evening lab choice.
  • The course's faculty show as ticked, in their current priority order.
  • A yellow "Editing " tag marks the box.
  • Reset becomes Cancel and Confirm becomes Save changes.

While editing:

  • Domain and Subject are locked. Slot and faculty can change.
  • Pressing another course's pencil cancels this edit and starts the new one.
  • Deleting the course being edited cancels the edit.

Save changes:

  • Replaces the course's slots and faculty with what's in the box, so a removed slot is gone.
  • Keeps the course in the same place in Your Courses.
  • If timetables were showing, regenerates them, keeps the filters and goes back to timetable 1.

Cancel leaves the course as it was and clears the box.

Each course remembers the school, programme, batch and domain it was added under, and editing uses those even if the navbar chip (#286) shows a different school. For courses saved before this change, look the subject up in the current school first, then in all schools.

Additional context

Needs #287 (Slot becomes a multi-selector) and the side-by-side layout (#290). Related: #285 (school popup), #252 (the popup this replaces).

Things in the current code to watch for:

  • Confirming a course that's already in the list merges into it and keeps its old slots (facultySelectorOnConfirm in landing.tsx), so Save changes can't reuse it as is.
  • Saved courses (fullCourseData) don't store a school or domain.
  • FacultySelector already re-ticks saved faculty when the subject and slot match a saved course, but it reads from localStorage. The edit can build on it but should read from the course list.
  • QuickModify.tsx is an unused stub that only logs to the console. Please remove it.

FacultySelector.tsx is also being split up in #266, so expect merge conflicts.

Design
Image
Example

One way to build it (just an idea):

  • Keep an editingCourseId in landing.tsx
  • Pass the course to FacultySelector to fill the form, and swap the button labels while it is set
  • Save changes replaces the course at the same index
<FacultySelector
  editingCourse={selectedCourses.find(c => c.id === editingCourseId)}
  onConfirm={editingCourseId ? saveEdit : facultySelectorOnConfirm}
  onCancelEdit={() => setEditingCourseId(null)}
/>
Dominant language
TypeScript
Stars
6
Forks
37
Avg merge
11h 13m
Merged PRs (30d)
55

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeChefVIT/ffcs

All issues in CodeChefVIT/ffcs

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.