Bug Reports

## Problem Statement The Collection Tracker is missing several features that users expect from a collection management tool: No export functionality No sharing capability No pricing/value information ## Area Collection Tracker ## Missing Features Detail ### 1. Export Functionality User Need: Ability to export collection data for backup, import into other tools, or personal records. Suggested Export Formats: CSV (spreadsheet compatible) JSON (developer/backup friendly) Plain text list PDF report (formatted summary) ### 2. Share Functionality User Need: Ability to share collection with others for trading, showing off, or collaboration. Suggested Share Options: Public link to view-only collection Private link with access code Social media sharing Direct share to other Flexslot users ### 3. Pricing Information User Need: See the monetary value of cards and total collection value. Suggested Pricing Features: Individual card prices (market/TCGPlayer/etc.) Total collection value Price trend indicators Value by set/rarity breakdown Price data source selection ## User Stories As a collector, I want to export my collection so I can back it up or use it in other tools As a collector, I want to share my collection so others can see what I have for trading As a collector, I want to see pricing information so I know the value of my collection ## Acceptance Criteria ### Export [ ] Add export button to Collection Tracker UI [ ] Support CSV export with all card data [ ] Support JSON export for data portability [ ] Include export options (all cards, filtered view, specific sets) ### Share [ ] Add share button to Collection Tracker UI [ ] Generate shareable public link [ ] Create view-only mode for shared collections [ ] Allow user to revoke/regenerate share links ### Pricing [ ] Integrate with pricing API (TCGPlayer, Scryfall, etc.) [ ] Display price per card in collection view [ ] Show total collection value summary [ ] Add price column to collection table [ ] Consider caching strategy for price data ## Questions for Stakeholder Which pricing source should be prioritized (TCGPlayer, CardKingdom, etc.)? Should prices be real-time or cached (with refresh option)? For sharing, should there be privacy controls (hide certain cards)? Should export include pricing data? ## Complexity Note This ticket contains 3 distinct features. Consider breaking into separate tickets: Collection Tracker: Export functionality Collection Tracker: Share functionality Collection Tracker: Pricing integration ## Reporter CaptainJack (user feedback)

## Problem Statement Users encounter a "Failed to add to collection" error when attempting to add a deck to a collection. This issue may be specifically related to creating a new collection during the add-deck-to-collection flow. ## Steps to Reproduce Open an existing deck Attempt to add the deck to a collection During the flow, create a new collection (rather than selecting an existing one) Observe the "Failed to add to collection" error ## Expected Behavior User should be able to add a deck to an existing collection successfully User should be able to create a new collection and add the deck to it in a single flow Success confirmation should be displayed after adding ## Actual Behavior Error message "Failed to add to collection" is displayed Deck is not added to the collection ## Acceptance Criteria [ ] Adding a deck to an existing collection works without errors [ ] Creating a new collection during the add-to-collection flow works correctly [ ] Deck appears in the target collection after successful addition [ ] Appropriate success/error feedback is displayed to the user [ ] Edge case: Handle scenario where collection name already exists ## Questions to Clarify Does this error occur when adding to existing collections, or only when creating new ones? Are there any specific error messages in the browser console or network requests? Does this affect all deck types or specific ones? --- Area: Collection Game: CaptainJack Type: Bug