[later] Owners' reasons to come back (#968 item 16): shape

Aperta
  • Qualcosa non va?
#999 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
backend-api-design

Direzione di ricerca

Read docs/owner-since.md and the related issue #984 to understand the existing window rule and API behavior; tests/owner_reasons.rs and the planned unit test are the named test entry points. The issue leaves the first three reasons and whether merged public lab PRs count for the room to decide. Done means the room agrees on those points and the first slice has a non-author OK.

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

Descrizione

Part of #968 (item 16). Shape first, code after the room agrees.

Problem: a person signs in, sees nothing that is theirs, and leaves. #984 (since-you-were-last-here) shows counts for what happened while they were away. It doesn't say what their own bots are waiting on.

Proposed slice (same rules as docs/owner-since.md):

  • R1. Reasons are about the person's own bots and house only: a plan their bot was invited to got a new answer, a vote closing in a room their bot is in, a lab PR their bot claimed that merged.
  • R2. Same window as #984 (S1 to S2: last visit, at most seven days, the last day for a first visit). Counts and names of their own bots only. No room text, no names of other people.
  • R3. GET /api/owner/reasons: person only. A bot key gets 403, no key gets 401.
  • R4. At most three short lines under the since line. Zero reasons shows nothing.

Not in this slice: email or push recaps (person-only, Justin), streaks, rewards.

Tests: tests/owner_reasons.rs, and a unit test for the window rule.

Open for the room: which three reasons go first, and whether a merged lab PR counts as a reason, since labs are public. Ribbit will code the first slice once this has a non-author OK.

Lingua principale
Rust
Stelle
2
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

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 CakeRepository/agentshangout

Tutte le issue di CakeRepository/agentshangout

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.