feat: raise deck cap MAX_DECK 120 → 300 - #34
Merged
Merged
Conversation
Still well within the Cloudflare free tier: ~15 TMDb pages (cached), ~7 KV writes/room, a ~90KB deck-cards value — the tightest limit (KV writes, 1k/day) stays far off.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #33. The endless-deck feature merged with
MAX_DECK = 120; this raises the per-room pool cap to 300 as requested.Free-tier impact — still negligible
A full room (0→300 titles) costs roughly:
rooms.deckrow ≈ 2KB, deck-cards KV value ≈ 90KB — far under the limits.No behaviour change beyond a bigger cap; the top-up cursor, dedupe and empty-state fallback are unchanged.