Group timetables that have the same slot layout

Abierto
  • ¿Algo no está bien?
#260 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
react, typescript
Área
frontend

Línea de trabajo

Start with src/lib/utils.ts and src/components/cards/ViewTimeTable.tsx to trace how timetable combinations are built and displayed. Compare layouts that differ only by faculty with layouts where one lab slot differs, then check how saving, sharing, filtering, and the timetable counter use the selected combination. Done means each unique layout appears once, its faculty alternatives remain accessible, and those actions still refer to the actual selection.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Right now, two timetables can look exactly the same in the grid but still appear as separate results just because a faculty is different.

For example, three faculty choices for the same course in the same slot shouldn't force someone to scroll through three identical-looking timetables.

What needs to be done

  • Build a consistent signature from the occupied slots/course arrangement.
  • Group combinations with the same layout while keeping all their faculty alternatives accessible.
  • Show each unique layout once, with a way to inspect or choose the faculty combinations within it.
  • Make sure saving, sharing, filtering and the timetable counter still refer to the actual selection.
  • Test cases where faculty differ but slots match, and where only one lab slot differs.

Likely files: src/lib/utils.ts, src/components/cards/ViewTimeTable.tsx.

Keep this separate from the generator optimization so the grouping logic is easy to verify.

Lenguaje dominante
TypeScript
Estrellas
7
Forks
39
Merge medio
10 h 59 min
PR fusionados (30 d)
62

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CodeChefVIT/ffcs

Todos los issues de CodeChefVIT/ffcs

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.