TIPS FOR TESTING THIS PART: Most Collection Hub accounts won't have any inventory, which means that there are no inventory fields in Firebase for that user either. This makes it difficult to test since nothing displays in the inventory page, so first you can first add to inventory from the Incoming Orders page (press add button). After the first write, all inventory fields will be populated in Firebase. From there, you can manipulate values in Firebase to display more items.
Overview: Implement inventory backend; includes 'add to inventory' feature (orders page) + inventory tab (profile page)
Screenshots:
Edited screens:
hub_screen.dart: connect Add To Inventory feature on orders page (incoming) to backend, connect inventory tab to backend
**NOTE: a to-do is to delete incoming orders cards after done adding to inventory, but since orders back-end isn't done, the card will just remain
TIPS FOR TESTING THIS PART: Most Collection Hub accounts won't have any inventory, which means that there are no inventory fields in Firebase for that user either. This makes it difficult to test since nothing displays in the inventory page, so first you can first add to inventory from the Incoming Orders page (press add button). After the first write, all inventory fields will be populated in Firebase. From there, you can manipulate values in Firebase to display more items.
Overview: Implement inventory backend; includes 'add to inventory' feature (orders page) + inventory tab (profile page)
Screenshots:
Edited screens: hub_screen.dart: connect Add To Inventory feature on orders page (incoming) to backend, connect inventory tab to backend **NOTE: a to-do is to delete incoming orders cards after done adding to inventory, but since orders back-end isn't done, the card will just remain
Edited files: state_widget.dart: added InventoryPage widget
Edited util: firestore_users.dart: added more API to connect inventory edits to firebase
Edited data model: user.dart: added CollectionHub class and related methods