1b51cb554b
All checks were successful
🚀 Deploy / 🧪 Test (pull_request) Successful in 1m33s
🚀 Deploy / ʦ TypeScript (pull_request) Successful in 1m16s
🚀 Deploy / 🔍 Lint (pull_request) Successful in 47s
🚀 Deploy / 🐳 Build (pull_request) Has been skipped
🚀 Deploy / 🚀 Deploy (pull_request) Has been skipped
When a manual pick triggered an immediate autodraft chain, both Discord announcements re-read currentPickNumber from the DB, which had already advanced past the chained pick. Both messages showed the same "On the clock" person, pinging them twice. Fix: pass nextPickNumber (the pick immediately following each specific pick, before any chain) as an explicit param to notifyPickMadeOnDiscord instead of re-reading from the DB. Also removes a now-unnecessary DB round-trip on every pick announcement. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| __tests__ | ||
| autodraft.update.ts | ||
| draft.adjust-time-bank.ts | ||
| draft.force-autopick.ts | ||
| draft.force-manual-pick.ts | ||
| draft.make-pick.ts | ||
| draft.pause.ts | ||
| draft.replace-pick.ts | ||
| draft.resume.ts | ||
| draft.rollback.ts | ||
| draft.start.ts | ||
| queue.add.ts | ||
| queue.clear.ts | ||
| queue.remove.ts | ||
| queue.reorder.ts | ||
| seasons.$seasonId.draft.ts | ||
| user.timezone.ts | ||
| watchlist.toggle.ts | ||