scheduling: let a booking and an availability query name a specific arrival window

Aperta
#2,731 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
openapi, rust

Direzione di ricerca

Start with crates/registry-scheduling-core/src/policy.rs around the start-based window selection cited in the issue, then inspect the generated OpenAPI document at products/scheduling/generated/registry-scheduling.openapi.json and the related clients. Trace admission, rescheduling, and availability entry points and their tests. Done means same-start windows publish and book independently, ambiguous requests return a clear problem code, availability supports window identifiers and filtering, and the OpenAPI document and clients are regenerated; coordinate with the linked source-published windows issue.

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

Descrizione

area:scheduling criticality:p2 enhancement triage:needs-implementation

Use case

Distinct sessions of one offering can start at the same time: two exam rooms at 09:00, or two activities at 19:00. Callers need to book a specific session and see availability per session.

Current evidence

  • A request picks its window by start, so two windows of one offering may not open together.
  • In the OpenAPI document, AdmissionRequest has no window field and AvailabilitySlot carries no window identifier.
  • The workaround is one offering per session. Each new offering needs a policy publication with the migration credential, which does not suit sessions created during normal operation.

Proposed behaviour

  • An optional window on admission and on a reschedule target.
  • A window identifier on each availability slot, and an optional window filter on availability.
  • Windows of one offering may share a start. A request that names no window, where the start is ambiguous, is refused with a problem that tells the caller to name the window.
  • Deployments without same-start windows behave exactly as today.

Acceptance criteria

  • Two windows of one offering with the same start publish, and each books independently up to its own units.
  • A request naming no window on an ambiguous start is refused with a clear problem code.
  • Existing single-window flows and their tests are unchanged.
  • Availability returns window identifiers and filters by window.
  • The OpenAPI document and clients are regenerated.

Delivery

Implemented in one PR with the source-published windows issue that follows this one.

Lingua principale
Rust
Stelle
2
Fork
0
Merge medio
9h 48m
PR unite (30g)
151

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 registrystack/registry-stack

Tutte le issue di registrystack/registry-stack

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.