/upcoming and /whos-in
- Lenguaje dominante
- HTML
- Estrellas
- 0
- Forks
- 0
- Merge medio
- 1 h 34 min
- PR fusionados (30 d)
- 23
Descripción
Two of the four commands. Both read-only, both ephemeral, neither edits anything.
- [ ] `/upcoming` — ephemeral agenda across every campaign the caller is on: date, session number, confirmed/in-jeopardy, their own intent. Replaces the idea of a pinned board: always current, no channel noise.
- [ ] `/whos-in` — authoritative roster state for the next (or a chosen) session, from D1, for when a post has gone stale. Includes flake memory where it says something.
- [ ] Register both in `src/discord/commands.ts` with the option shapes; `npm run commands:register`.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Start with the command definitions and option shapes in src/discord/commands.ts, then inspect the existing campaign, session, and D1 data paths used by Discord commands. Run npm run commands:register after adding both registrations. Done means /upcoming and /whos-in provide the listed read-only, ephemeral agenda and roster information for the relevant campaigns and sessions.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- typescript
- Área
- backend, databases
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Activo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 55/100