Skip to content

docs(sdk): teach the built-in interface model - #189

Draft
librowski wants to merge 1 commit into
feat/ui-ext-2-testsfrom
feat/ui-ext-3-docs
Draft

librowski wants to merge 1 commit into
feat/ui-ext-2-testsfrom
feat/ui-ext-3-docs

Conversation

@librowski

@librowski librowski commented Oct 1, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

The guides teach only the new model from #187. Hand-written prose only; the API reference is generated from the JSDoc in #187.

Changes

  • build-a-plugin.md gains "Built-in interface: hide, move, add" with the hide-and-recreate example, a plugin that mounts through OptionalAppChildren, and the model's boundaries. The slot table marks the deprecated slots with their replacements.
  • custom-jsonforms-control.md points controls to PropertiesPanelFooterContent and PropertiesPanelMenuItem.
  • Demo and plugins-core READMEs switch to the new components.
  • ui-extensions.decision-log.md records the decisions behind feat(sdk)!: built-in controls, state hook, actions, content areas, menu items and onStart #187 and the follow-ups: menu-item-identity, deprecated-slot-warning, restore-toast-source, palette-empty-state, public-type-naming, built-in-control-components, plugin-as-component, read-only-import-settings.

Part 3 of 4 in a stack: #187 code -> #188 tests -> #189 docs -> #190 place. Review in order. When #187 merges, GitHub retargets #188 to main, and so on.

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