@get-bb/plugin-sdk 0.5.31 → 0.6.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -4
- package/bundled-types/bb-plugin-sdk-app.d.ts +261 -102
- package/bundled-types/bb-plugin-sdk-internal-composer-handle.d.ts +457 -0
- package/bundled-types/bb-plugin-sdk-internal-host-policy.d.ts +21 -4
- package/bundled-types/bb-plugin-sdk-testing-app.d.ts +32 -10
- package/bundled-types/bb-plugin-sdk-testing.d.ts +8 -3
- package/bundled-types/bb-plugin-sdk.d.ts +295 -109
- package/dist/app.js +2 -0
- package/dist/internal/composer-customization-validation.js +37 -27
- package/dist/internal/composer-handle.js +531 -0
- package/dist/internal/plugin-app-collector.js +37 -27
- package/dist/testing/app.js +780 -132
- package/dist/testing/index.js +6 -2
- package/package.json +7 -1
package/README.md
CHANGED
|
@@ -13,9 +13,13 @@ the built-in `bb-plugin-authoring` skill synchronized with those declarations.
|
|
|
13
13
|
|
|
14
14
|
Composer UI extensions register through `app.composer.customize(...)`. A
|
|
15
15
|
`ComposerCustomization` can contribute React action and banner components,
|
|
16
|
-
host-rendered `ComposerPlusMenuItem`
|
|
17
|
-
Mounted components use `useComposer()
|
|
18
|
-
|
|
16
|
+
host-rendered `ComposerPlusMenuItem` and `ComposerSendMenuItem` rows, and
|
|
17
|
+
`ComposerRichTextSpec` rules. Mounted components use `useComposer()`: one
|
|
18
|
+
stable handle for the composer's text, mentions, picker selection, scope,
|
|
19
|
+
layout, run and submit state, writes, effects, and input locking. Selection is
|
|
20
|
+
reactive and is `null` for composers without pickers. Panels and pages that
|
|
21
|
+
write into a composer the user picks use `useComposers()`, one handle per
|
|
22
|
+
composer on screen.
|
|
19
23
|
Any mounted plugin component can use
|
|
20
24
|
`useBbNavigate().openThreadPanel(...)` to request one of the
|
|
21
25
|
same plugin's registered thread-panel actions; it returns false when the
|
|
@@ -70,7 +74,7 @@ app-wide floating React UI. BB mounts the component once per app window through
|
|
|
70
74
|
the normal plugin slot boundary, so SDK hooks and plugin CSS work and React
|
|
71
75
|
context survives portals. This app-level boundary includes the sidebar thread
|
|
72
76
|
data and action hooks. Hooks whose contract requires a particular surface,
|
|
73
|
-
including `useComposer
|
|
77
|
+
including `useComposer`, remain limited to that surface.
|
|
74
78
|
The plugin owns the overlay's chrome, positioning, visibility, focus, and
|
|
75
79
|
responsive behavior; a crashing overlay is hidden without affecting siblings.
|
|
76
80
|
Use a content script for app-wide DOM behavior that does not need React context.
|