render_component
Render a catalog component in your running app, capture a screenshot, and return runtime diagnostics including console errors and failed network requests to visually confirm changes work.
Instructions
Render a catalog component in the running app and return a screenshot plus runtime diagnostics (console errors, uncaught exceptions, failed network requests). Resolves the component to its URL automatically via the route map — just name the component you changed. Use this to visually confirm a change actually works. Requires the dev server to be running.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| route | No | Optional: render a raw route path directly instead (e.g., "/patients/:id"). Use instead of `component`. | |
| params | No | Values for dynamic route segments, e.g. {"id": "123"}. If omitted, sensible placeholders are guessed. | |
| public | No | Skip the configured login pre-step for this call — use for public routes so a broken/missing credential can't block them (default false). | |
| fullPage | No | Capture the full scrollable page instead of just the viewport (default false). | |
| settleMs | No | Extra milliseconds to wait after load before screenshotting (e.g. for animations). | |
| component | No | Catalog component name to render (e.g., "PatientDetail"). The route map resolves it to a URL. |