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

オープン
#2,731 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
52/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
openapi, rust

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Rust
スター
2
フォーク
0
平均マージ
9時間 48分
マージ済み PR(30日)
151

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

registrystack/registry-stack のほかの issue

registrystack/registry-stack の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。