Public wishlist buy flow

[a-type]

For items in the public wishlist, there needs to be a way to mark purchases.

Ideas

Click "Shop idea." A modal opens explaining this is just an idea the person had and shows various online shop search buttons with prefilled queries. Final action: set a quantity, click "Bought #"

Products

If there's an embedded buy link in the card, the card action should be "Bought this." The modal just has quantity set and "Bought #"

Vibes

Click "Shop vibe." A modal opens with the vibe description and a large format image/gallery. Shop search buttons again. No quantity needed, just "Bought" Not even sure a final action is relevant to this really.

[a-type]

Technical reqs for public buying:

• Need public anon mutation for purchasing an item from a list. Should require a token embedded in the page to prevent random usage.
• Buys should include item id, quantity and the name of the buyer (optional?)
• When serving the list page, purchased count on items should be augmented with aggregated buy counts associated with the item
• Bought items should probably still be rendered, but at the bottom and obviously marked as purchased.

[a-type]

Applying public purchases....

Main problem is syncing nom-live data to a live document without missing any or duplicates.

Two approaches....

Keep a running set of applied purchase IDs on the list and don't apply one twice. Downside: monotonically growing set.

Or, keep a "last applied date" and avoid applying purchases before that date. Downside: more complicated when a visibility cutoff date is in play.

Given the number of public purchases is not likely to exceed the hundreds, even unbounded set seems fine.

But we can also clean out the set whenever the req for purchases comes back empty.

Btw purchases should be confirmed. Confirmed purchases get a confirmed timestamp and don't come back in the request next time. You can still req them with a filter to view purchases history.