-
fix(podcasts): clarify episode max_tokens field and fix empty-state error (#1197)
发布于
2026-07-21 01:10:50 +00:00 | 58 次提交 在此版本后已推送到 mainThe episode profile "Max output tokens" field (#991) confused users:
nothing explained what it controls, and whether it was a
per-conversation, per-turn, or per-call limit. An empty field also
showed "Must be a positive integer" — a scary error on an optional
field — because a transient/empty number-input state produced NaN,
which slipped past the nullable() guard into the positive() rule.- Add help text (all 14 locales) stating it caps output tokens per
generation step — the outline and the full transcript, not a per-turn
or conversation limit — and that blank uses the built-in defaults
(3000 outline / 5000 transcript, from podcast-creator). - Add a placeholder ("Leave blank for defaults") so the empty field
reads as intentionally optional rather than unfilled. - Map empty and NaN inputs to null in setValueAs, so an empty or
half-typed value reads as "unset" and never trips the positive-integer
rule. Genuinely invalid entries (0, negatives, decimals) still error.
Field stays an optional override — no behavior change to generation.
Verified in the browser: help renders, placeholder shows, empty field
has no error, zero console errors. Frontend lint/test/build green.下载附件
- Add help text (all 14 locales) stating it caps output tokens per