Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Widget: copy a completed assistant reply

Aperta
#477 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@piyusshhjangid ci sta già lavorando.

Dal 30/10/2026.

  • #504 di @piyusshhjangid — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

hacktoberfest
What problem would this solve?

Visitors often need to reuse an answer outside the chat. Selecting a long rendered reply is awkward on phones and can be error-prone around formatted text and code blocks.

What would you like to happen?

Add a copy action to completed assistant replies. Copy the reply as readable plain text, preserving code block contents and line breaks without copying Markdown syntax. Keep the action out of the streaming state, make it keyboard accessible, and announce success or failure without disrupting the existing reply announcement.

Where to look
  • packages/widget/src/dom/messages.ts renders assistant messages and reply actions.
  • packages/widget/src/i18n.ts holds the widget’s accessible UI strings.
  • packages/widget/src/styles/widget.css contains message action styles.
  • packages/widget/tests/dom/messages.test.ts covers message rendering.
Acceptance criteria
  • A copy button is available for a completed assistant reply and is not shown while that reply is streaming.
  • Clipboard failures are handled without an uncaught error, including when the Clipboard API is unavailable.
  • The control has a localized accessible name, a visible focus indicator, and an accessible confirmation of the result.
  • Tests cover copying formatted content, streaming replies, and clipboard failure.
  • Add a widget changeset; keep the gzipped bundle within the configured size budget.
Contributing
  • I’d like to work on this myself
Lingua principale
TypeScript
Stelle
13
Fork
7
Merge medio
3h 28m
PR unite (30g)
296

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di codercops/chatcops

Tutte le issue di codercops/chatcops

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.