Skip to content

fix(tui): keep btw dialog in plugin context - #49828

Closed
opencode-agent[bot] wants to merge 1 commit into
v2from
btw-dialog-crash
Closed

opencode-agent[bot] wants to merge 1 commit into
v2from
btw-dialog-crash

Conversation

@opencode-agent

Copy link
Copy Markdown
Contributor

Fixes #49777

Summary

  • capture the active markdown renderer while the built-in /btw app slot is still under PluginProvider
  • pass it into the sibling answer dialog instead of calling usePlugin() outside the provider boundary
  • add a fixture-driven regression test covering /btw submission through rendered answer

Tests

  • bun test test/feature-plugins/btw.test.tsx --timeout 30000
  • bun test test/plugin-markdown.test.tsx test/app-lifecycle.test.tsx --timeout 30000
  • bun typecheck

Requested by: @rekram1-node (Aiden Cline via Slack)

Capture the markdown renderer from the app slot before opening the sibling dialog, so rendering a generated /btw answer no longer calls usePlugin outside PluginProvider. Add a fixture-driven regression test for the complete slash-command flow.
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.

1 participant