Better custom cart fragment typing

[theocerutti]

Hello,

When we create a cart with a custom CART_QUERY_FRAGMENT it creates an incorrect ts typing.
Actually, even with your DEFAULT_CART_QUERY_FRAGMENT the typing is not correct.
If we have to modify the behavior of the cart it's really annoying since we have to override almost every cart types and that's because of almost one big issue.

So if we create a cart with custom query:

export const CUSTOM_CART_QUERY_FRAGMENT = `#graphql
fragment CustomCartApiQuery on Cart {
    id
    checkoutUrl
    totalQuantity
}`;

const cartHandler = createCartHandler({
  storefront,
  getCartId: cartGetIdDefault(request.headers),
  setCartId: cartSetIdDefault(),
  cartQueryFragment: CUSTOM_CART_QUERY_FRAGMENT,
  cartMutateFragment: CUSTOM_CART_QUERY_FRAGMENT,
});

Then theses types:

type CartReturn = Cart & {
    errors?: StorefrontApiErrors;
};
type CartQueryData = {
    cart: Cart;
    userErrors?: CartUserError[] | MetafieldsSetUserError[] | MetafieldDeleteUserError[];
};

should be:

import { CustomCartApiQueryFragment } from 'storefrontgenerated.ts'; 

type CartReturn = CustomCartApiQueryFragment & {
    errors?: StorefrontApiErrors;
};
type CartQueryData = {
    cart: CustomCartApiQueryFragment;
    userErrors?: CartUserError[] | MetafieldsSetUserError[] | MetafieldDeleteUserError[];
};

Indeed we shouldn't have Cart as type but the real queried fragment: CustomCartApiQueryFragment in this case.

---

also CartGetProps should allow to add more custom fields since we could add parameter to cart query fragment:
it would be nice to have a dynamic CartGetProps: we could "read" the custom query fragment and add variable type dynamically to CartGetProps.
otherwise just add a extraQueryVariables prop:

type CartGetProps = {
    ...
    extraQueryVariables: any[];
};

[juanpprieto]

I agree this is a valid feature request. I've create an issue to get this officially in our backlog

[ricky-harrys]

We are also facing this issue. Thanks for raising it @theocerutti