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

Create @chatcops/store-cloudflare (D1, KV and a Durable Object counter)

Aperta
  • Qualcosa non va?
#249 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@bhushan4work ci sta già lavorando.

Dal 21/10/2026.

  • #296 di @bhushan4work — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
postgresql, typescript
Ambito
backend, database, distributed-systems

Direzione di ricerca

Start with packages/core/src/storage/types.ts, runStorageConformance from @chatcops/core/testing, and CONTRIBUTING.md’s “Writing a store package” section; inspect the SQLite store and its tables in issue #247. Use Miniflare from a normal Node test and run conformance against D1 + KV + DO and D1 alone as specified. Done means the acceptance checks pass, including 50 exact Durable Object increments, README Wrangler configuration, a minor changeset, and the listed build, coverage, lint, and publint commands.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement hacktoberfest help wanted server

A ChatCops server on Cloudflare Workers keeps everything in memory today, and Workers isolates come and go all the time, so conversations and rate limits barely last. This package stores them in Cloudflare's own services.

This is a bigger one, for someone who has had a few PRs merged here and knows Workers. The interfaces and the tests it has to pass already exist: packages/core/src/storage/types.ts and runStorageConformance from @chatcops/core/testing. CONTRIBUTING.md has a "Writing a store package" section with the package layout.

What to do
Create packages/store-cloudflare:

import { cloudflareStorage, ChatCopsCounter } from '@chatcops/store-cloudflare';
export { ChatCopsCounter };   // the Durable Object class, exported from the Worker

storage: cloudflareStorage({ d1: env.DB, kv: env.CHATCOPS_KV, counters: env.CHATCOPS_COUNTERS })
  • d1 is required:
    • It stores conversations (with append, updateMessage, removeMessage, list, purge) and events (with query).
    • Use the same tables as the SQLite store (see #247). D1 is SQLite, so the schema can be shared later.
    • D1 has no interactive transactions, so make append atomic with db.batch(). The version check has to be part of the statements themselves, for example UPDATE ... SET version = version + 1 WHERE id = ? AND version = ?, with the inserts conditional on it.
  • counters: a Durable Object namespace when given. Durable Objects run one request at a time, so increments are exact; ship the ChatCopsCounter class. Without one, fall back to a D1 UPSERT ... RETURNING. Never use KV for counters: it's eventually consistent.
  • kv: Workers KV when given, otherwise a D1 table. Workers KV can't do an atomic setIfAbsent, so only offer setIfAbsent on the D1 table.
  • Include a wrangler.jsonc snippet in the README with the D1 binding, the DO binding and its migration.
  • "private": true in package.json. A maintainer publishes it for the first time.

Testing
Use Miniflare from a normal Node test (new Miniflare({ ... d1Databases, kvNamespaces, durableObjects }) and its getD1Database() etc.) rather than the Workers vitest pool, which doesn't mix well with the root vitest projects here. Workers KV has a 60 second minimum TTL, so pass skip: ['kv-ttl'] for the KV-backed run, and run the suite a second time on the D1-only setup without skipping it.

Acceptance criteria

  • runStorageConformance passes with D1 + KV + DO (skipping only kv-ttl) and with D1 alone (nothing skipped)
  • 50 concurrent increments through the Durable Object land exactly
  • README with the wrangler config
  • Changeset for @chatcops/store-cloudflare (minor)
  • pnpm -r build, pnpm test:coverage (90% lines, 80% branches for store packages), pnpm lint and pnpm publint 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.

Lingua principale
TypeScript
Stelle
13
Fork
7
Merge medio
3h 41m
PR unite (30g)
155

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.