Skip to content

Include the complete public TypeScript SDK surface in API exports #20268

Description

Is there an existing issue for this?

  • I have searched the existing issues.

Part of #20258. No prerequisite sibling issue; related consumer mismatch: #17608.

Is your feature request related to a problem? Please describe the problem.

Canonical output omits public bootstrap functions such as createBuilder, connect, and refExpr. Support types have abbreviated declarations, and owned aliases can lack documentable nodes.

Describe the solution you'd like

  • Inventory public generated/support-module exports and re-exports, with explicit private/internal exclusions.
  • Add missing symbols and complete their declarations using current metadata fields; make any necessary symbol-kind additions compatibly here.
  • Preserve ownership and distinguish complete public definitions from foreign dependency stubs.
  • Add symbol/member/declaration parity checks against generated SDKs and support modules, accounting for aliases and augmentation.

Independent delivery: Complete public surface coverage can ship on the current canonical schema without richer metadata from #20266 or scanner changes. Own new symbol kinds and their writer/tests here; do not redesign shared metadata fields or introduce another signature projector. Tests verify surface parity, not absence of every known documentation gap. Other-language exporters remain separate.

Additional context

Bootstrap emission. Compiled core exports reproduce the omissions. Raw capability-ID differences alone are not a missing-API count.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions