Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Turn protocol v1 parts into the old stream format, for widgets before 0.6

Geschlossen
  • Stimmt etwas nicht?
#240 2 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@Saifjafri212213 arbeitet bereits daran.

Seit 20.10.2026.

  • #259 von @Saifjafri212213 — gemerged

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

core enhancement good first issue hacktoberfest

The 0.6 server streams typed parts (WirePart, in packages/core/src/protocol/v1.ts), but widgets on 0.5 and older read chunks like {"content":"Hi"} and {"done":true}. Those widgets will stay on sites and CDNs for months, so the server needs to translate. This issue is that translation, as one pure function.

What to do
Create packages/core/src/protocol/legacy.ts:

export interface LegacyChunk {
  content?: string;
  done?: boolean;
  error?: string;
  retryAfter?: number;          // seconds
  leadCaptured?: boolean;
  leadData?: Record<string, unknown>;
  suggestedActions?: string[];
}

/** The chunk an old widget expects for this part, or null for parts it has no use for. */
export function toLegacyChunk(part: WirePart): LegacyChunk | null;
v1 part Legacy chunk
text-delta { content: delta }
lead-captured { leadCaptured: true, leadData: lead }
suggestions { suggestedActions: items }
error with rate_limited { error: 'rate_limit', retryAfter }, with retryAfter = retryAfterMs rounded up to seconds, left out when there's none
error with timeout { error: 'timeout' }
error with internal_error { error: 'internal_error' }
error with invalid_request { error: 'Invalid request' } (what 0.5 servers send)
error with any other code { error: 'provider_error' }
finish with reason error or aborted null (the error part already went out, or nobody is listening)
finish with any other reason { done: true }
everything else (start, text-start, text-end, source, tool-call, tool-result, handoff, agent-message) null

Those error strings are the ones the 0.5 widget understands (packages/widget/src/widget.ts, resolveErrorType, line 643).

Where to look

  • packages/core/src/protocol/v1.ts (the part types)
  • packages/server/src/handler.ts, which writes the old chunks today (lines 51, 61, 71, 181, 209, 223, 250)

Acceptance criteria

  • New packages/core/src/protocol/legacy.ts, exported from packages/core/src/protocol/index.ts and from @chatcops/core
  • One test per row of the table, plus retryAfterMs: 1500 becoming retryAfter: 2
  • A test that runs a whole v1 stream through it and gets the exact chunks a 0.5 server sends for the same reply
  • Changeset for @chatcops/core (minor)
  • pnpm test:coverage and pnpm lint pass

Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off dev, and open your PR against dev with Closes #<this issue number>. Setup notes (pnpm, build before test) are in CONTRIBUTING.md.

Vorherrschende Sprache
TypeScript
Sterne
13
Forks
7
Ø Merge
3 Std. 33 Min.
Gemergte PRs (30 T.)
176

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus codercops/chatcops

Alle Issues in codercops/chatcops

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.