scheduling: let a booking and an availability query name a specific arrival window
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
- Bereich
- backend-api-design
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
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,
AdmissionRequesthas no window field andAvailabilitySlotcarries 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
windowon admission and on a reschedule target. - A window identifier on each availability slot, and an optional
windowfilter 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
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus registrystack/registry-stack
-
area:breg enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
registrystack/registry-stack#2765 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
registrystack/registry-stack#2761 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
registrystack/registry-stack#2743 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
registrystack/registry-stack#2706 ·
Maintainer antworten meist innerhalb von 1 Tag
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directoryOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 83/100
registrystack/registry-stack#2704 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in registrystack/registry-stack
Ähnliche Issues
-
area:web kind:bug priority:p2 ready
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 85/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 80/100
sims1253/ry#931 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 84/100
sims1253/r-typeshed#140 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
storytold/craft-libs#2867 ·
Maintainer antworten meist innerhalb von 1 Tag
-
help wanted needs investigation priority: low
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100