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

Offen
#2,731 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
52/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
openapi, rust

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Rust
Sterne
2
Forks
0
Ø Merge
9 Std. 48 Min.
Gemergte PRs (30 T.)
151

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus registrystack/registry-stack

Alle Issues in registrystack/registry-stack

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.