Skip to content

Document exposed ports for reusable subcircuit interfaces#794

Open
rushabhcodes wants to merge 4 commits into
tscircuit:mainfrom
rushabhcodes:agent/document-subcircuit-port-interfaces
Open

Document exposed ports for reusable subcircuit interfaces#794
rushabhcodes wants to merge 4 commits into
tscircuit:mainfrom
rushabhcodes:agent/document-subcircuit-port-interfaces

Conversation

@rushabhcodes

@rushabhcodes rushabhcodes commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Summary

  • explain how <port /> defines connection points in symbols and subcircuits
  • show how connectsTo exposes an internal component pin
  • demonstrate external connections with selectors such as FILTER.INPUT
  • document direct-child port behavior with showAsSchematicBox
  • cross-link the port and subcircuit references
  • update the port props table with pinNumber, aliases, and connectsTo

Added in Port docs

image

Added in Subcirucit docs

image

Why

The existing port reference described ports as symbol-only and did not explain how to expose stable connection points from reusable subcircuits.

Validation

  • bun run typecheck
  • bun run build
  • verified exposed subcircuit port behavior against the core regression test

@vercel

vercel Bot commented Jul 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jul 14, 2026 11:35am

Request Review

@rushabhcodes
rushabhcodes marked this pull request as ready for review July 14, 2026 11:11
Copilot AI review requested due to automatic review settings July 14, 2026 11:11

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@github-actions

Copy link
Copy Markdown

This PR has been automatically marked as stale because it has had no recent activity. It will be closed if no further activity occurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants