refactor: retire redirected course readers without changing legacy URLs

Abierto
  • ¿Algo no está bien?
#73 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
48/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
next.js, react, typescript
Área
developer-experience, frontend

Línea de trabajo

Start by tracing imports from src/app/courses/ and the reader components, then check next.config.ts and the protection helpers to distinguish retired code from shared code. Use e2e/checks.mjs and the reader and redirect browser checks to verify legacy URLs preserve nested paths and query strings, render the dashboard destination, and keep unknown destinations at 404. Done when only unreferenced legacy components are removed, architecture guidance names the canonical reader, and the listed checks pass.

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

Descripción

enhancement help wanted

Problem

next.config.ts permanently redirects /courses and /courses/:path* to /dashboard, but the repository retains a second course-reader route tree and its reader components. This makes it harder for contributors to identify the active implementation.

Scope

  • Inventory the legacy route/component import graph and confirm which files are unreachable through the supported application routes.
  • Remove only duplicate pages/components whose sole consumers belong to that retired tree.
  • Preserve the existing permanent redirects, path segments and query strings.
  • Keep the active dashboard reader, content safety rules and any shared helpers still used elsewhere.
  • Update architecture guidance to identify the canonical reader.
  • Treat this as dead-code cleanup; it does not fix an active reading restriction or change the student reading experience.

Starting files

next.config.ts, src/app/courses/, src/app/components/Reader/, src/app/components/Protected/NoCopyWrapper.tsx, src/hooks/useContentProtection.ts, e2e/checks.mjs and docs/architecture.md.

Done when

Tests verify direct legacy requests redirect to the matching dashboard URL, including nested unit paths and query strings. Browser checks confirm the destination renders the expected content and unknown destinations still return 404. Lint, typecheck, unit tests, production build and reader/redirect browser checks pass. Removed components have no remaining consumers.

Lenguaje dominante
TypeScript
Estrellas
1
Forks
1
Merge medio
8 h 58 min
PR fusionados (30 d)
37

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 procoderji-com/procoderji

Todos los issues de procoderji-com/procoderji

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.