🥔✨ `Marketplace`: Buying 🥡 `Products` #1326

zspencer · 2023-04-08T20:47:23Z

🥔🗜️✨ Gizmo: Marketplace #831

Use Cases

Domain Model

Bugs

🐞 Marketplace: Buying Products: Guest Shopper is shown a 404 after Checkout` #1657
🐞 Marketplace: Buying Products: Saving Delivery Details on Checkout when no Cart Delivery Area is set #1983
🐞 Marketplace: Buying Products: Changing DeliveryArea does not update the Cart DeliveryFee #2002
🐞 Marketplace: Buying Products: Switching Marketplaces should not destroy your Cart #1962
🐞 Marketplace: Buying Products - Can't Checkout when only one unarchived DeliveryArea #2198

The text was updated successfully, but these errors were encountered:

…ent` - #1325 - #1324 - #1326 I didn't use the `marketplace_order, :full` factory outside of the `Order::PlacedMailerPreview` and `Order::ReceivedMailerPreview`; and apparently had flubbed the implementation; so that was not working... So I fixed it and used it in the `Order::EmailReceiptComponent` spec to test the `Order#delivery_area` I also noticed we didn't wire in associations between the `Marketplace::DeliveryArea` into the `Marketplace::Cart` and `Marketplace::Order` so I added some specs for those.

…ent` (#1332) - #1325 - #1324 - #1326 I didn't use the `marketplace_order, :full` factory outside of the `Order::PlacedMailerPreview` and `Order::ReceivedMailerPreview`; and apparently had flubbed the implementation; so that was not working... So I fixed it and used it in the `Order::EmailReceiptComponent` spec to test the `Order#delivery_area` I also noticed we didn't wire in associations between the `Marketplace::DeliveryArea` into the `Marketplace::Cart` and `Marketplace::Order` so I added some specs for those.

- #1326 - #1187 - 🛠️ `Components`: Makes sure Tailwind notices `Furniture`'s `Component` files - 🧹 `Components` I'm not sure if this is the right path or not but it decouples our `ButtonComponent` from the `button.scss` file, and makes it a bit easier to override the defaults for how we present buttons. - 🌸 Gets rid of the extra `Marketplace::Cart::Delivery::EditButtonComponent` that hangs out underneath the cart - 🌸 Tailors the `Marketplace::Cart::Delivery::EditButtonComponent` better for smaller screens.

* 🌸🛠️🧹 `Marketplace`: Tidy up `Marketplace#show` - #1326 - #1187 - 🛠️ `Components`: Makes sure Tailwind notices `Furniture`'s `Component` files - 🧹 `Components` I'm not sure if this is the right path or not but it decouples our `ButtonComponent` from the `button.scss` file, and makes it a bit easier to override the defaults for how we present buttons. - 🌸 Gets rid of the extra `Marketplace::Cart::Delivery::EditButtonComponent` that hangs out underneath the cart - 🌸 Tailors the `Marketplace::Cart::Delivery::EditButtonComponent` better for smaller screens. * 🧹`Components`: Consolidate `margin` and `padding` as `spacing` Again, not sure this is a great idea but I wanted some way to partially overload the default classes a component uses.

- #1326

- #1326 - #1324 This is wildly insufficient, but it gets us to the point where we're able to test that the way we're calling `Stripe::Checkout::Session.create` is at least *close* to what it's supposed to be called with. It would be far better to get a `spec/furniture/marketplace/system` that actually hits Stripe...

`Marketplace`: Get a test on the `Checkout` - #1326 - #1324 This is wildly insufficient, but it gets us to the point where we're able to test that the way we're calling `Stripe::Checkout::Session.create` is at least *close* to what it's supposed to be called with. It would be far better to get a `spec/furniture/marketplace/system` that actually hits Stripe...

- #1428 - #1326 A quick insertion of the photos into the cart view. We probably should do a broader redesign pass on the `Cart` UI 🔜 but this seems decent enough?

#1326

- #2043 - #1326 While we definitely need a `Cart`; treating the `Cart` as the `Menu` is a clunky ducky way of operating. I'm going to start driving towards a more `Menu` centric approach so the Shopping experience looks and feels a bit less nerd-forward. Theoretically, this will entail: - [ ] Sprouting `Product#show` - [ ] Ditching the `Marketplace::Cart` ui almost completely, perhaps? - [ ] Updating `buying_products_system_spec.rb`

- #1326 The aspect ratio is now 16x9, which should be easier for people to just "naturally" upload. The width of the small hero variant is edge-to-edge full-def on Apple's current highest-end device, the iPhone 15 Pro Max. There's probably a way smarter way of doing this that uses say, background images and CSS selectors to load just-the-right-sized image for the particular use-case; but I figure going big-and-downscaling is probably better from a "make pretty" perspective.