Skip to content

fix: forward svgExportRenderer from the starter route - #3

Open
Sokanon wants to merge 1 commit into
pixel-point:mainfrom
Sokanon:fix/forward-svg-export-renderer
Open

fix: forward svgExportRenderer from the starter route#3
Sokanon wants to merge 1 commit into
pixel-point:mainfrom
Sokanon:fix/forward-svg-export-renderer

Conversation

@Sokanon

@Sokanon Sokanon commented Sep 6, 2026

Copy link
Copy Markdown

Summary

ToolcraftApp accepts svgExportRenderer, and docs/toolcraft/core/setup-export.md tells products to declare a typed export-svg action and provide ToolcraftAppComposition.svgExportRenderer. The starter's src/routes/index.tsx forwards every other composition prop but not that one, so a generated app cannot mount the documented SVG export path: the output-export contract requires the renderer for a typed SVG action, and the route is framework-owned, so the app can't patch it locally without failing the integrity check.

Change

One line in starter/src/routes/index.tsx: pass svgExportRenderer={appComposition.svgExportRenderer} alongside the other props.

Verified

tsc --noEmit on the starter is green with the change. Hit this while building a pattern tool on the starter that needed a vector export.

ToolcraftApp accepts svgExportRenderer and the export docs tell products
to provide it for a typed export-svg action, but the starter route never
passed it through, so a generated app could not mount the documented SVG
export path at all. The route now forwards it like every other
composition prop.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant