You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(admin): honour escape sequences in form-view string fields (#8211)
The settings form view rendered string values in single-line <input>s.
Browsers strip line breaks from an input's value, so values such as
defaultPadText lost their newlines, and anything typed (e.g. `\n`) was
JSON-encoded again on save, producing `\\n` in settings.json and a literal
backslash-n in the pad text. Env placeholder defaults were shown in raw
escaped form but re-escaped on save, with the same result.
String inputs and env placeholder defaults now show values in their
JSON-escaped form and decode typed escape sequences before writing, so
`Welcome\n\ntest\n` is stored exactly like a hand-edited settings.json.
Incomplete escapes (a trailing backslash while typing) are not propagated.
Fixes#8211
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012kA75NPq8nGRidAwhPXeCi
0 commit comments