Export reviewed lab occurrences as an ICS file (optional v1 increment)

Abierto
  • ¿Algo no está bien?
#36 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, nodejs

Línea de trabajo

Read AGENTS.md and docs/PROJECT_CONTEXT.md, then inspect the calendar projection and the dependency issue #35; implementation must wait until its contracts land and the design is discussed with the maintainer. Add an ICS serializer with tests and docs, covering escaping, line folding, timezones, stable UIDs, and unknown or cancelled entries. Done means exported fixtures pass an independent validator and the relevant checks listed in the issue pass.

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

Descripción

area:backend area:docs priority:medium status:blocked type:feature

Part of #28 · Target: Optional / not a v1 release blocker

Goal and scope

Offer opt-in export of resolved occurrences with deterministic UID, timezone semantics, source links and explicit handling of unknown/cancelled/moved entries. Keep output private and let user choose export destination.

Implementation starting points

calendar projection, new ICS serializer, tests and docs. Follow AGENTS.md and docs/PROJECT_CONTEXT.md; reuse existing authorization, safe-error and synthetic-fixture patterns. New runtime dependencies need a documented reason.

Dependencies and readiness

Depends on #35. Discuss the design before starting implementation; dependent contracts must land first.

Out of scope

No Google/Outlook synchronization, subscriptions, silent file overwrite, automatic exports or reminders.

Acceptance criteria and test plan

Validate ICS escaping, CRLF/folding, DST/timezones, stable UID updates and injection-shaped titles. Unknown dates/times cannot silently become invented events. Parse exported fixtures with an independent validator. This task may move after v1 without blocking the release.

Run the relevant offline tests, npm run check and git diff --check; runtime changes also require npm test and npm audit. Report checks not run. No faculty credentials or private course material are required for a contribution.

Contributing

Comment here before starting so the maintainer can coordinate the approach and avoid duplicate work. Fork the repository, branch from master, and open a focused PR referencing this issue. No assignee or delivery deadline is set; required checks and review apply.

Lenguaje dominante
JavaScript
Estrellas
0
Forks
0
Merge medio
1 h 20 min
PR fusionados (30 d)
14

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 mahmutmft/courses-mcp

Todos los issues de mahmutmft/courses-mcp

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.