Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Edit a course from Your Courses with a pencil button

Offen
  • Stimmt etwas nicht?
#291 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@Aiden-Trindade arbeitet bereits daran.

Seit 28.10.2026.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
43/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
react, typescript
Bereich
frontend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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)}
/>
Vorherrschende Sprache
TypeScript
Sterne
6
Forks
37
Ø Merge
11 Std. 13 Min.
Gemergte PRs (30 T.)
55

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus CodeChefVIT/ffcs

Alle Issues in CodeChefVIT/ffcs

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.