Commit graph

12 commits

Author SHA1 Message Date
d5332ccee5 Make WeaponGrid responsive 2022-02-02 23:39:06 -08:00
4fb2fd16b8 Fix optimistic UI and prevent saving identical uncap values 2022-02-02 20:36:22 -08:00
ecfc62900d Trading working uncap indicators for working party creation
We start storing the party ID here so that we know (and can come to know) when we are working with an existing party.

Updating the weapon grid based on `weapons` the state vs `props.weapons` makes saving items to a party work properly.

Unfortunately, it sends us back to square one with debouncing the uncap indicators.
2022-02-02 19:07:10 -08:00
065c198e67 Fix uncap indicator optimistic ui update bug 2022-02-02 18:43:55 -08:00
827473ee5a Refactor object grids to handle business logic instead of Party 2022-02-02 16:54:14 -08:00
4f0844c378 Cleanup and refactoring 2022-02-01 14:19:44 -08:00
39549f0b94 Move debounce to WeaponGrid 2022-02-01 11:40:06 -08:00
dd974fde2e WIP: Use debounce to intelligently send uncap level to server
We are using debounce to send the uncap level to the server without making a ton of requests if the user is feeling clicky.

This is a WIP because it doesn't send to the server yet. I'm having issues setting the correct initial state from the props.
2022-02-01 05:07:52 -08:00
7a50c4bce5 Pass down GridWeapon instead of Weapon
Previously, we stripped the Weapon out of the GridWeapon for simplicity. However, now that we need to display and manipulate data on the GridWeapon (unique data), we need to pass that down instead.
2022-02-01 05:06:27 -08:00
d56bdb58f8 Fix bug with mainhand position 2022-01-30 03:09:20 -08:00
3bdb048f28 Move SearchModal to WeaponGrid 2022-01-28 23:10:21 -08:00
728803d9c5 Migrate to Next.js 2022-01-24 21:54:50 -08:00