feat(studio): render with preview variables + template handoff + docs#2051
Open
Conversation
Collaborator
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jul 8, 2026
jrusso1020
force-pushed
the
07-07-feat_studio_variables_inspector_panel_with_live_preview_values
branch
from
c17a78a to
dc052d3
Compare
jrusso1020
force-pushed
the
07-07-feat_studio_render_with_preview_variables_template_handoff_docs
branch
from
619fd88 to
b6b3f61
Compare
Sixth PR of the template-variables Studio stack — closing the loop from
preview to render to developer handoff.
- renders started from the Renders tab now carry the active preview
variable overrides (StartRenderOptions.variables → POST /render →
RenderConfig.variables), so "render" produces exactly what the user is
previewing.
- Variables panel "Use this template" footer: copy the effective values
(defaults merged with overrides) as JSON, or as a ready-to-run
`npx hyperframes render <comp> --variables '<json>'` command.
- gitignore: negate the renders/ output rule for the tracked
src/components/renders/ source dir — without it, pre-commit's format
re-stage (`git add {staged_files}`) hard-fails on any change to those
files.
- docs: the Studio panel docs/concepts/variables.mdx described was
aspirational — replace with the real Variables-in-Studio section
(declare/edit, render-truthful preview, render-with-values, handoff,
usage badges); document the new SDK variable APIs in
docs/sdk/reference/composition.mdx (declaration ops, read APIs,
setPreviewVariables).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jrusso1020
force-pushed
the
07-07-feat_studio_variables_inspector_panel_with_live_preview_values
branch
from
dc052d3 to
f2a1662
Compare
jrusso1020
force-pushed
the
07-07-feat_studio_render_with_preview_variables_template_handoff_docs
branch
from
b6b3f61 to
8254c95
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Sixth PR of the template-variables stack: closing the loop from preview to render to developer handoff.
StartRenderOptions.variables→POST /render→RenderConfig.variables) — you render exactly what you're previewingnpx hyperframes render <comp> --variables '<json>'command (shell-quote-safe — see feat(studio): variables inspector panel with live preview values #2050's review fixes for the quoting helper).gitignore: negate therenders/output rule for the trackedsrc/components/renders/source dir — without it, the pre-commit format re-stage (git add {staged_files}) hard-fails on any change to those filesdocs/concepts/variables.mdxdescribed an aspirational Studio panel — replaced with the real Variables-in-Studio section; the new SDK variable APIs documented indocs/sdk/reference/composition.mdxWhy
Copy-a-working-command is the highest-leverage developer handoff pattern (the command reflects current panel state and runs as-is), and render-what-you-preview is the whole point of making preview injection render-truthful.
Test plan
{"variables":{"title":"Render Me"}}to/api/projects/vars-demo/renderwith the override active🤖 Generated with Claude Code