You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 useOrderDerails deprecated
Create orderDataProvider composable 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
The text was updated successfully, but these errors were encountered:
Description
Currently, the
useOrderDetails
composable has 2 roles:Data provider -
loadOrderDetails
method byorderID
that is a "constructor" parameterBusiness logic executor - methods allowing actions on the order object.
This assumption is problematic because:
Solution:
useOrderDerails
deprecatedorderDataProvider
composable for fetching datauseOrderData?
composable for getting data from the orderUse Case
.
Proposed Solution
No response
Alternatives Considered
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: