fix: start new schedules enabled, keep ws versions off created variables

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ViTUkt4czrvZdxdWwxqRAQ
This commit is contained in:
Diego Imbert
2026-09-11 19:24:17 +02:00
co-authored by Claude Opus 5
parent 185d0fcd37
commit 7c39415c3a
2 changed files with 6 additions and 2 deletions
@@ -361,7 +361,9 @@
</div>
{#snippet actions()}
<OpenInSessionButton source={sessionSource} />
{#if edit && curWs}
<!-- Only for a variable opened for editing: one created here holds the other workspaces
under its temporary key, which names nothing in them. -->
{#if editPath !== undefined && curWs}
<WsSpecificVersions kind="variable" workspaceId={curWs} {initialPath} bind:selected />
{/if}
<Button
@@ -253,7 +253,9 @@ export async function newScheduleCfg(opts: NewScheduleOptions): Promise<Schedule
cron_version: s?.cron_version ?? 'v2',
timezone: s?.timezone ?? Intl.DateTimeFormat().resolvedOptions().timeZone,
paused_until: s?.paused_until ?? undefined,
enabled: s?.enabled ?? false,
// A create always enables the schedule (`writeScheduleCfg`), so that is where a new one
// starts: the deployed side a create records is the value it sent.
enabled: true,
summary: s?.summary ?? '',
labels: s?.labels ?? undefined,
description: s?.description ?? '',