The CartItemsApi supports passing the optional include parameter (line_items.physical_items.options and/or line_items.digital_items.options) on a cart item request. That same include parameter is applicable to the CartsApi, but doesn't exist in the Aligent library.
The impact of that include parameter not being available on CartsApi is that abbreviated cart data is returned when you retrieve cart info, so modifiers and the options that create a given variant don't exist on each cart item. That option data is critical for each cart item so that all chosen options can be displayed.
Moreover, because BigCommerce does not have a get endpoint for individual cart items (only for the cart as a whole) there's no way of retrieving that cart item option data. Having the optional include parameter on CartItemsApi only means that the option data will be returned when you add or update a cart item, but is otherwise unavailable.
jswift
commented
2 years ago
The CartItemsApi supports passing the optional include parameter (line_items.physical_items.options and/or line_items.digital_items.options) on a cart item request. That same include parameter is applicable to the CartsApi, but doesn't exist in the Aligent library.
The impact of that include parameter not being available on CartsApi is that abbreviated cart data is returned when you retrieve cart info, so modifiers and the options that create a given variant don't exist on each cart item. That option data is critical for each cart item so that all chosen options can be displayed.
Moreover, because BigCommerce does not have a get endpoint for individual cart items (only for the cart as a whole) there's no way of retrieving that cart item option data. Having the optional include parameter on CartItemsApi only means that the option data will be returned when you add or update a cart item, but is otherwise unavailable.