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
We still use the transaction ID since it is allows for the code to compile and does not break anything (since the user choice is just displayed on UIs and not used for any further computations).
I would propose to use the basketID + reward item in basket as parameter value for generateSpendRequestResponse when calling it from the promotion service.
The text was updated successfully, but these errors were encountered:
Emerged from issue #75.
We still use the transaction ID since it is allows for the code to compile and does not break anything (since the user choice is just displayed on UIs and not used for any further computations).
I would propose to use the basketID + reward item in basket as parameter value for generateSpendRequestResponse when calling it from the promotion service.
The text was updated successfully, but these errors were encountered: