Skip to content

Admin build a bear#302

Merged
3TTemi merged 9 commits intomasterfrom
admin-build-a-bear
Apr 6, 2026
Merged

Admin build a bear#302
3TTemi merged 9 commits intomasterfrom
admin-build-a-bear

Conversation

@jjasonguo
Copy link
Copy Markdown
Contributor

@jjasonguo jjasonguo commented Mar 23, 2026

Summary

This PR Is the backend changes required for the build a bear admin dashboard.

  • modified dto, gateway, service
  • added .spec testing files that probably should have been there before
    • Wire Up State Management in the Admin
  • Create admin ui components

TODO:

  • talk to temi about how we want prod to be updated / maintained

Test Plan

Added unit tests

Notes

Breaking Changes

@dti-github-bot
Copy link
Copy Markdown
Member

dti-github-bot commented Mar 23, 2026

[diff-counting] Significant lines: 1152. This diff might be too big! Developer leads are invited to review the code.

@3TTemi
Copy link
Copy Markdown
Collaborator

3TTemi commented Mar 24, 2026

Looking good, 2 backend requests:

  1. When a bear item is deleted, the DB correctly removes related inventory/equipped rows via cascade, but I don’t think we notify affected users that their inventory/loadout changed. We only emit updateBearItemData exits (saying the item no longer exists, not the user lost the item). Can we also push refreshed updateUserInventoryData / updateUserBearLoadoutData to users with the deleted item so the frontend doesn’t keep a stale state?

  2. Changing a bear item’s slot using the admin seems unsafe because UserBearEquipped.slot is stored separately and won’t automatically follow BearItem.slot. Can we block slot edits or migrate/clear equipped rows on slot change?

@jjasonguo
Copy link
Copy Markdown
Contributor Author

Looking good, 2 backend requests:

  1. When a bear item is deleted, the DB correctly removes related inventory/equipped rows via cascade, but I don’t think we notify affected users that their inventory/loadout changed. We only emit updateBearItemData exits (saying the item no longer exists, not the user lost the item). Can we also push refreshed updateUserInventoryData / updateUserBearLoadoutData to users with the deleted item so the frontend doesn’t keep a stale state?
  2. Changing a bear item’s slot using the admin seems unsafe because UserBearEquipped.slot is stored separately and won’t automatically follow BearItem.slot. Can we block slot edits or migrate/clear equipped rows on slot change?

Makes sense, added return to default for erasing equipped items and removed slot changing

@3TTemi 3TTemi merged commit 91ae604 into master Apr 6, 2026
13 checks passed
@3TTemi 3TTemi deleted the admin-build-a-bear branch April 6, 2026 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants