mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-26 02:00:52 +01:00
The live issue page renders IssueChatThread, not CommentThread, so port the reply-to-comment UI there per the CTO routing decision: - onAdd/runtime gain a 4th replyToCommentId param; the composer forwards it via runConfig.custom (dropped on the reassign path, matching the server contract) - Composer reply chip (quoted/clamped source, jump-to-original, X to clear, Escape-to-clear on empty editor, persisted via the shared :reply draft key) - Hover Reply button on human + genuine agent comment bubbles - Sent quoted block above replies (accent-aware for the blue human bubble), jump-to-original scroll + highlight, and deleted-source tombstone - Reply state lifted into IssueChatThread and exposed to bubbles via context; composer ref merged so a bubble Reply focuses the composer Existing CommentThread implementation + shared comment-reply helpers unchanged. tsc -b ui green; issue-chat-messages tests green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@paperclipai/ui
Published static assets for the Paperclip board UI.
What gets published
The npm package contains the production build under dist/. It does not ship the UI source tree or workspace-only dependencies.
Storybook
Storybook config, stories, and fixtures live under ui/storybook/.
pnpm --filter @paperclipai/ui storybook
pnpm --filter @paperclipai/ui build-storybook
Typical use
Install the package, then serve or copy the built files from node_modules/@paperclipai/ui/dist.