impress/app/views/outfits
Matchu 7a3aa609ba Use the main app for outfit saving, not impress-2020
This came in a few parts!
1. Add meta tags to let us know we're logged in.
2. Install React Query, which has the data-loading sensibilities I like
   about Apollo without the GraphQL that has honestly been a drag.
3. Replace the outfit-loading and outfit-saving calls with API calls to
   the main app.
4. Update the main app's API calls to use our more flexible data
   constructs like "pose".

Would've loved to do this more incrementally, but it's hard to! You
can't split out outfit-loading and outfit-saving, or auth from any of
that, or the state gets all out-of-sorts.

Still, this is a good nugget we've pulled out all-in-all, and one that
people have been asking for! Can maybe look to logged-in item search
soon too, for own/want data?
2023-11-02 16:54:35 -07:00
..
_outfit.html.haml Remove slightly-broken edit outfit links from user outfits page 2023-10-24 18:05:51 -07:00
edit.html.haml Use the main app for outfit saving, not impress-2020 2023-11-02 16:54:35 -07:00
index.html.haml i18n for outfits#index - plus the translate_with_links helper, which can be used for refactoring other stuff 2013-01-09 17:15:25 -06:00
new.html.haml Update most URLs to use HTTPS 2023-10-25 15:22:57 -07:00