Summary#

Backend code that also runs in API or headless modes cannot assume frontend-only structures will exist or keep the same type. Defensive normalization at the boundary is usually cheaper and safer than scattering special cases across business logic, especially for optional viewport, session, or editor state.

Problem#

Server-side nodes expected a dict populated by the UI, but in API mode the same field arrived as a string, causing type errors when backend code indexed into it.

Solution#

Coerce malformed or non-dict values to safe defaults at input boundaries and access optional fields with tolerant lookups such as .get(). Define explicit fallback semantics for no-UI execution so downstream code can proceed without special casing every caller.

Failure Modes#

• Headless/API execution crashes on assumptions inherited from the browser client
• Schema drift between UI and API transports goes unnoticed until runtime
• Fallback defaults are inconsistent across components, leading to partial behavior differences

Sources#

• https://github.com/Comfy-Org/ComfyUI/pull/14939
• https://github.com/Comfy-Org/ComfyUI/pull/14928
• https://github.com/Comfy-Org/ComfyUI/pull/14930
• https://github.com/Comfy-Org/ComfyUI/pull/14924
• https://github.com/Comfy-Org/ComfyUI/pull/14920
• https://github.com/Comfy-Org/ComfyUI/pull/14917
• https://github.com/Comfy-Org/ComfyUI/pull/14761
• https://github.com/Comfy-Org/ComfyUI/pull/14762
• https://github.com/GitHubDaily/GitHubDaily/pull/267
• https://github.com/GitHubDaily/GitHubDaily/pull/52
• https://github.com/fastapi/full-stack-fastapi-template/pull/2382
• https://github.com/fastapi/full-stack-fastapi-template/pull/2380
• https://github.com/fastapi/full-stack-fastapi-template/pull/2373
• https://github.com/fastapi/full-stack-fastapi-template/pull/2379
• https://github.com/fastapi/full-stack-fastapi-template/pull/2363
• https://github.com/fastapi/full-stack-fastapi-template/pull/2364
• https://github.com/fastapi/full-stack-fastapi-template/pull/2333
• https://github.com/fastapi/full-stack-fastapi-template/pull/2375
• https://github.com/react/react/pull/37009
• https://github.com/react/react/pull/36913
• https://github.com/thedaviddias/Front-End-Checklist/pull/664
• https://github.com/thedaviddias/Front-End-Checklist/pull/680
• mined_at: 2026-07-14T22:08:42Z

Sagwan Revalidation 2026-07-14T22:48:11Z#

• verdict: ok
• note: 경계 정규화와 안전 기본값 권장은 현재도 유효한 일반 원칙이다.

Sagwan Revalidation 2026-07-16T23:53:06Z#

• verdict: ok
• note: 일반적 경계 정규화 원칙으로 최근 practice와 충돌 없어 재사용 가능

Sagwan Revalidation 2026-07-19T01:33:56Z#

• verdict: ok
• note: 경계 정규화 권장은 여전히 유효하며 특정 수치 의존도 낮음

Sagwan Revalidation 2026-07-21T02:46:07Z#

• verdict: ok
• note: 경계에서 UI 입력을 정규화하라는 권장안은 여전히 보편적으로 유효함.