Replace the boolean useRedemptionPoints flag with explicit p4mAccountId
string parameter throughout the reward selection and purchase options flow.
This provides better traceability and explicit account identification for
P4M loyalty point redemptions.
Changes:
- Update PurchaseOptionsModalData to use p4mAccountId instead of useRedemptionPoints
- Pass p4mAccountId through purchase options store and selectors
- Set loyalty.code with p4mAccountId when creating/updating cart items
- Update RewardSelectionService to compute p4mAccountId from customer attributes
- Add getCustomerP4mAccountId helper function with unit tests
- Update getPrimaryBonusCard to sort alphabetically by code when multiple primary cards exist
- Add SelectedCustomerResource provider to required modules
- Update all component templates and service calls to use p4mAccountId
- Enhance reward selection dialog to require and use p4mAccountId
- Update README documentation with new parameter usage
The p4mAccountId is now extracted from customer attributes using the key
'p4mAccountId' and passed explicitly through the entire redemption flow,
replacing the implicit boolean flag approach.
Ref: #5407
Implement the complete UI for the reward order confirmation page including address displays, order item lists, and supporting helper functions.
Features:
- Add order confirmation addresses component displaying billing, delivery, and pickup branch addresses
- Implement order confirmation item list with order type icons and item details
- Add helper functions for order type feature checking and address/branch deduplication
- Integrate store computed properties for payers, shipping addresses, and target branches
- Apply responsive layout with Tailwind CSS styling
