3 Commits

Include renames

Author	SHA1	Message	Date
timothyandClaude Opus 4.8	8090e10408	fix(api): #265 — If-Match evaluates per RFC 7232 (valid-but-non-matching → 412, not 400) ... The shared optimistic-concurrency parser (ConcurrencyHeaders.ParseIfMatch) classified any non-canonical/weak/list If-Match value as Malformed → 400. Per RFC 7232 §3.1 a syntactically -valid entity-tag that simply doesn't strong-match must be 412; 400 is only for a genuine grammar violation. - Rewrite ParseIfMatch as a real RFC 7232 entity-tag/list parser: walks the comma-separated 1#entity-tag list, validates each [W/]DQUOTE *etagc DQUOTE member, and collects the strong members whose opaque text is our canonical decimal. Weak / empty / non-canonical / out-of-range tags are valid but contribute no version (→ empty set → 412); genuine grammar violations (unquoted, SP-in-tag, unterminated, garbage) → 400. - Reshape IfMatchCondition.ExpectedVersion : Option<int> → ExpectedVersions : Option<Seq<int>> and VersionedAggregateExtensions.CheckVersion → set membership (any strong match proceeds; empty set always 412). Threads through 10 replace/update commands + handlers + request mappers + 9 controllers. - No wire-contract change (400 + 412 already declared on every PUT; the field is header-derived and internal — no DTO/route/response-type/OpenAPI change). - Tests: ConcurrencyHeadersTests rewritten for the new classification (lists, weak, empty, non-canonical → Version/empty-set; grammar violations → Malformed) + new VersionedAggregateExtensionsTests for CheckVersion membership/empty-set/force-write. - Docs: api-conventions.md §7a rewritten; decisions.md entry appended. Refs #253 #197 fixes #265 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-12 23:09:36 +02:00
timothyandClaude Opus 4.8	c40ffefa99	feat(253): PR3 optimistic-concurrency fan-out — Diff + Scalar aggregates ... Fans the frozen Block recipe (api-conventions §7a) across the five Diff/Scalar replace-all endpoints, completing the #253 PR2→PR4 arc's implementable core: - #6 Collection custom-order, #7 Playout alternate-schedules, #8 Playout templates (shared Playout.Version), #9 MultiCollection, #10 RerunCollection — each: pre-check 412 as a standalone Either after validation (H2, subtype survives the Join flatten), unconditional Version++ (M1), guarded save, controller If-Match/ETag/400/412, SPA editor ETag round-trip + 412 conflict dialog. - H1: the two Playout handlers' catch(Exception)→422 restructured so the guard's PreconditionFailedError returns before the catch (412, not 422). - M2: RerunCollection/Collection refresh runs unconditionally on save; MultiCollection keeps its name-only→no-rebuild optimization by bumping on the first (name) save. - H3: UpdateDefaultDecoHandler bulk-bumps Playout.Version via .SetProperty. - Shared ConcurrencyHeaders.MalformedIfMatchProblem() for the 400 guard. - Deferred (→ #269): same-root non-bulk sibling config writers' ETag rotation. Tests: per-handler pre-check/bump concurrency tests (Playout ×2 incl. non-vacuous racing-save backstop, Rerun, Multi incl. name-only-no-rebuild M2, Collection); controller tests get a DefaultHttpContext for the header read/write. Docs: api-conventions §7a fan-out status, spa-conventions §4a list-editor note, decisions. Refs #253 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-11 19:23:48 +02:00
timothyandClaude Fable 5	f1b3879d51	feat(api): playout erase/scheduling-context + collection custom-order (#210, #211) ... Backend slice for the ChicoryTV playouts and collections screens. PlayoutController: - POST /api/playouts/{id}/erase-items (204; 404 pre-check; 422 unless Block/Sequential/Scripted) -> ErasePlayoutItems - POST /api/playouts/{id}/erase-items-and-history (204; 404; 422 unless Classic/Block/Sequential/Scripted) -> ErasePlayoutHistory - GET /api/playouts/items/{id}/scheduling-context (200/404) decodes a playout item's stored context by row id via a new GetPlayoutItemSchedulingContext query that reuses ProcessSchedulingContext - PlayoutItemResponseModel gains HasSchedulingContext (no raw JSON in list) - PlayoutListItemResponseModel gains PlayoutMode (ChannelNumber already present) CollectionController: - PUT /api/collections/{id}/custom-order (204; 404 pre-check; 422) with UpdateCollectionCustomOrderRequest deriving CustomIndex from array order - GetCollectionItemsHandler orders by CustomIndex (nulls last) then title/id when the collection's UseCustomPlaybackOrder is set Tests: controller route + behavior tests, OpenAPI ProblemDetails TestCases, GetCollectionItems custom-order handler test. Regenerated v1.json, v1.d.ts, endpoint-index.md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-09 22:05:51 +02:00