frontends
frontends copied to clipboard
[FEATURE] Add more flexibility to the useOrderDetails
Description
Currently, the useOrderDetails composable has 2 roles:
Data provider - loadOrderDetails method by orderID that is a "constructor" parameter
Business logic executor - methods allowing actions on the order object.
This assumption is problematic because:
- Order data can be already fetched by different data providers (order email success page)
- Order can be identified not only by ID (deepLinkCode)
Solution:
- Make
useOrderDerailsdeprecated - Create
orderDataProvidercomposable for fetching data - Create
useOrderData?composable for getting data from the order
Use Case
.
Proposed Solution
No response
Alternatives Considered
No response
Additional Context
No response