Skip to content

bug: clip dialogs send no fps or resolution; the api applies the operator's - #636

Merged
lukepolo merged 1 commit into
mainfrom
bug/clip-dialogs-no-settings-read
Sep 29, 2026
Merged

lukepolo merged 1 commit into
mainfrom
bug/clip-dialogs-no-settings-read

Conversation

@lukepolo

Copy link
Copy Markdown
Contributor

Clip fps and resolution stay admin-only settings; the api already enforces them on every render (5stackgg/api#461), so the clip dialogs neither read nor send them.

  • CreateClipDialog, ClipEditorBar and RenderHighlightForPlayerDialog lose their resolution pickers and settings reads; requests carry no fps, resolution or output
  • the Highlights settings page is back on the admin-only clip_fps / clip_resolution names and no longer says users can override the resolution; unused clips.*.resolution keys dropped; zeus ClipSpecInput.output is optional

Merge/deploy: api#461 is merged; deploy it (migration + metadata on boot) before this web, since the editor now omits output.

Tests: clipOutputOperatorOnly.spec.ts (5) fails on main and passes here; full vitest green, check-translations 16/16.

…ator's

Removes the resolution pickers and clip-setting reads from the clip editor,
preset dialog and admin highlight dialog, and puts the Highlights settings
page back on the admin-only clip_fps/clip_resolution names.
@lukepolo
lukepolo merged commit e47f79c into main Sep 29, 2026
2 checks passed
@lukepolo
lukepolo deleted the bug/clip-dialogs-no-settings-read branch September 29, 2026 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant