From d953789ecc06bbb9114483ee992929dd81c26dff Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Bombeck?= Date: Mon, 19 Oct 2026 16:43:54 +0200 Subject: [PATCH] chore: spell the value-range separator as an escape The template key in the measurement list carried a literal NUL byte, which made tools treat the file as binary. --- src/components/measurements/measurement-list.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/components/measurements/measurement-list.tsx b/src/components/measurements/measurement-list.tsx index 1e5e4f795..625be97a8 100644 --- a/src/components/measurements/measurement-list.tsx +++ b/src/components/measurements/measurement-list.tsx @@ -425,7 +425,7 @@ export function MeasurementList({ // never a history entry per keystroke); an external URL change (back // button, deep link) re-seeds the draft via the render-phase derived-state // adjustment below, exactly like the vault's search field. - const urlValueRange = `${filters.valueMin ?? ""}${filters.valueMax ?? ""}`; + const urlValueRange = `${filters.valueMin ?? ""}\u0000${filters.valueMax ?? ""}`; const [valueDraft, setValueDraft] = useState(() => ({ min: filters.valueMin ?? "", max: filters.valueMax ?? "",