Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#249 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
postgresql, typescript
Domaine
backend, database, distributed-systems

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
13
Forks
7
Merge moyen
4 h 11 min
PR mergées (30 j)
122

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de codercops/chatcops

Toutes les issues de codercops/chatcops

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.