-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Noticed that the current implementation of loader state for all 3 cards (Product, Wishlist and Cart) are using the same shared context state,
- This firstly might go against the concept of a global shared state with context
- This results in one API request triggering loader for all cards on the page
This issue is more apparent and visible on the cart page, when user tries to either remove the product or move to wishlist
Suggestions:
- Have separate state for all 3 cards, will result in repetitive states but each will be unique to only that card, ensuring each component is triggered does not affect other children
Metadata
Metadata
Assignees
Labels
No labels