graphql_commerce 3.0.0-beta2

Cart, checkout and profile operations now follow the same rules as the Commerce cart and checkout forms. All sites using the Commerce GraphQL extensions should update.

Changes

• Cart queries and mutations resolve carts through the Commerce cart provider and entity access handlers.
• commerceAddToCart validates that the quantity is a positive integer.
• Quantity changes compute the stock delta from the item's current quantity, and a rejected quantity no longer changes the item.
• Cart and checkout responses are not cached.

Behaviour changes for API consumers

• commerceGetCart, commerceGetCarts, commerceAddToCart and commerceCheckout only act on the current user's or session's carts. An account/accountId argument other than the current user returns an error or an empty result.
• commerceGetCarts returns the current user's carts; the orderType and storeId filters still apply.
• Cart mutations (commerceAddToCart, commerceCartChangeQuantity, commerceRemoveFromCart, commerceEmptyCart, commerceApplyCoupon, commerceRemoveCoupon) only change active carts. Locked order items, such as items added by a promotion, cannot be changed or removed.
• commerceCheckout requires the access checkout permission and follows Commerce's checkout access rules. Customers can still open their own placed order, for example on the completion step.
• commerceEditProfileForm requires update access to the profile.
• CommerceProduct.variation(id:) only returns variations the user can view and otherwise falls back to the default variation.