mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-07 18:26:17 +00:00
JamesandClaude Fable 5
2e0b884521
Fourth PR of the template-variables Studio stack — the HTTP plumbing.
- preview routes (/preview and /preview/comp/*) accept
?variables=<url-encoded json> and inject
`window.__hfVariables = {...}` into <head>, before the runtime and any
composition script — the exact global the engine sets via
evaluateOnNewDocument at render time, so preview-with-values cannot
diverge from render output. Values are escaped against </script>
breakout, malformed payloads 400 instead of silently previewing
defaults, and the ETag is salted with a hash of the payload so cached
previews revalidate when values change.
- POST /projects/:id/render accepts variables ({variableId: value}) and
forwards them through StudioApiAdapter.startRender into the producer's
RenderConfig.variables — the same channel `hyperframes render
--variables` uses. Wired in both adapters (CLI embedded server + vite
dev adapter).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
12 lines
476 B
TypeScript
12 lines
476 B
TypeScript
/**
|
|
* Shared shape check for composition-variable payloads (`?variables=` on the
|
|
* preview routes, `body.variables` on the render route) — one contract, one
|
|
* error string, so the routes can't drift.
|
|
*/
|
|
|
|
export const VARIABLES_PAYLOAD_ERROR = "variables must be a JSON object of {variableId: value}";
|
|
|
|
export function isVariablesPayload(value: unknown): value is Record<string, unknown> {
|
|
return typeof value === "object" && value !== null && !Array.isArray(value);
|
|
}
|