-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
updateCart #11
Comments
Yeah lack of consistency. Also, the current implementation of checkout and addCartProduct needs to be redone: We have a big feature request at a customer who needs to have multiple carts per user for his requirements. I guess we could fix this while implementing the new "Multi-Cart" feature, consistently asking for the orderId to update. |
I will solve these requirements like this: New cart convenience mutations:
Renamed (BREAKING):
New order manipulating mutations in preparation of "multi-cart":
That way, a very simple checkout is possible without fetching the orderId once in one big query but the full feature set is only available when using the indirect methods. |
Done in PR #18 |
currently, checkout and addCartProduct works without providing the orderId of the cart.
on the other hand, if you want to update the order with e.g. the billig address, you have to know the orderID.
introduce a updateCart mutation to fix that
The text was updated successfully, but these errors were encountered: