Resolve lab cancellations, moved sessions and conflicting evidence

Aperta
  • Qualcosa non va?
#33 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, node.js
Ambito
backend-api-design

Direzione di ricerca

Read the forum evidence model, occurrence resolver, and src/labs.js, along with AGENTS.md and docs/PROJECT_CONTEXT.md. First review dependencies #29 and #32 and discuss the authority and applicability design with the maintainer before implementation. Done means the listed evidence cases are covered, partial evidence never confirms an absence, moved sessions retain stable identities, and the required checks are reported.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Part of #28 · Target: Scheduling / v0.5

Goal and scope

Apply explicitly dated/group-scoped cancellation or move evidence to occurrences. Preserve original and replacement references, publication/effective dates and unresolved conflicts. Establish authority/applicability rules with a reviewed design.

Implementation starting points

forum evidence model, occurrence resolver, src/labs.js. 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 #29, #32. Discuss the design before starting implementation; dependent contracts must land first.

Out of scope

No interpreting unrelated announcements as cancellation, silent evidence precedence or notifications.

Acceptance criteria and test plan

Tests cover one-group cancellation, moved room/day/time, superseded timetable, unrelated post, conflicting updates and failed announcement refresh. Partial evidence never becomes confirmed absence; stable identities avoid duplicated moved sessions.

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.

Lingua principale
JavaScript
Stelle
0
Fork
0
Merge medio
1h 20m
PR unite (30g)
14

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di mahmutmft/courses-mcp

Tutte le issue di mahmutmft/courses-mcp

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.