Skip to content

Canvas & Extensions authoring API: out-of-scope for 1.0.0 GA #121

Closed as not planned

Description

@krukow

Generated via Copilot on behalf of @krukow

Canvas & Extensions: declare out-of-scope for 1.0.0 GA (or implement post-GA)

Found during the GA upstream parity audit (Phase 1).

The Node.js SDK exposes a Canvas / Extensions authoring surface that this SDK does not implement:

  • Session config fields for canvas/extension registration.
  • A session getter for canvas state.
  • A canvas authoring API.

What this SDK does already do: the generated wire layer parses and coerces the
related session events (session.canvas.opened, session.canvas.registry_changed,
session.extensions.attachments_pushed), and they are now in the public event-types
set (see the F2 fix). So canvas/extension activity is observable even though the
authoring API is absent.

Decision for GA

Treat the canvas/extensions authoring API as out-of-scope for 1.0.0 GA and
document it as a known limitation (the observable events remain supported). Revisit
implementing the authoring surface post-GA based on demand.

Upstream references (tag v1.0.0-beta.12):

  • nodejs/src/types.ts — canvas/extension config fields
  • nodejs/src/session.ts — canvas getter

Severity: post-ga.

Activity

  1. krukow commented on Jul 15, 2026

    @krukow
    CollaboratorAuthor

    Generated via Copilot on behalf of @krukow

    Closing as not planned.

    The canvas/extensions authoring surface is intentionally out-of-scope for the GA line. What matters for parity is already covered: the generated wire layer parses and coerces the related session events (session.canvas.opened, session.canvas.registry_changed, session.extensions.attachments_pushed) and they are in the public event-types set, so canvas/extension activity is fully observable today. The authoring API is an additive, non-breaking surface we can introduce post-GA without violating the frozen contract.

    No user has requested the authoring API, and the upstream surface is still evolving. Reopen (or file a fresh issue) if there's concrete demand — implementing it later costs nothing in compatibility.

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

    post-gaDeferred to after 1.0.0 GA

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions