January 10, 2025 (canary)

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

Patch Changes

• 026114e - Sovle issue where showValid would be forwarded to the textField element (@paales)

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

Patch Changes

• 5ca6fb9 - When a user reorders their cart without interacting with their cart previously a new cart wouldn't be created. (@paales)

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

@graphcommerce/[email protected]

January 06, 2025 (canary)

@graphcommerce/[email protected]

Patch Changes

• #2477 8015eab - Upgraded to @apollo/client 3.12.3 without impacting typescript compilation performance. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2477 8015eab - Upgraded to @apollo/client 3.12.3 without impacting typescript compilation performance. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2477 8015eab - Upgraded to @apollo/client 3.12.3 without impacting typescript compilation performance. (@paales)

January 06, 2025 (canary)

@graphcommerce/[email protected]

Patch Changes

• #2473 f085c89 - Solve issue where the ProductListItemsBase was already wrapped in a form. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2473 8df172e - Do not warn about :first-child since all css is hoisted out of the components. (@paales)

• #2473 b076b2a - Also accept false as value for sxx (@paales)

January 06, 2025 (canary)

@graphcommerce/[email protected]

Patch Changes

• #2470 f5565b4 - Moved all test routes files to the demo package so they are out of the example directory. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2470 910e6aa - Refactor the FormComponents for better TypeScript checking performance. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2470 8f047a0 - Modify the type that is exposed for createTheme, should be faster for TypeScript to check. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2470 29e2956 - Components must have Theme parameter to avoid significant compiler slowdown. (@paales)

January 03, 2025 (canary)

@graphcommerce/[email protected]

Patch Changes

• #2472 905157b - Solve issue with chalk compilation because we’re not migrated to esm modules. (@paales)

GraphCommerce 9.0.3

@graphcommerce/[email protected]

Patch Changes

• #2469 3e5ee65 - Magento 2.4.6-p7 and lower: Solve a schema incompatibility for PlaceOrderError type on the PlaceOrderOutput. (@paales)

December 30, 2024 (canary)

@graphcommerce/[email protected]

Patch Changes

• #2469 3e5ee65 - Magento 2.4.6-p7 and lower: Solve a schema incompatibility for PlaceOrderError type on the PlaceOrderOutput. (@paales)

GraphCommerce 9.0.2

@graphcommerce/[email protected]

Patch Changes

• 7d5e75e - Solve issue where the Component prop would we forwarded tot the DOM element of the PaymentMethodActionCard (@paales)

• 058b7bf - Support Magento 2.4.7 placeOrder.errors field to handle possible errors while placing the order. An assertOrderPlaced method was created to assert a valid placed order. (@paales)

@graphcommerce/[email protected]

Patch Changes

• 30d769e - Make sure we are toggling the selected shipping method when a user selects a previously selected shipping method (@paales)

@graphcommerce/[email protected]

Patch Changes

• 6b28b60 - Make sure we are correctly selecting the shipping method form when a user selects a previously selected method again. (@paales)

@graphcommerce/[email protected]

Patch Changes

• 058b7bf - Support Magento 2.4.7 placeOrder.errors field to handle possible errors while placing the order. An assertOrderPlaced method was created to assert a valid placed order. (@paales)

@graphcommerce/[email protected]

Patch Changes

• dc70489 - Support Magento 2.4.7 placeOrder.errors field when placing a Mollie order (@paales)

@graphcommerce/[email protected]

Patch Changes

• c40c559 - Solve an issue where the payment submission would remain in a spinning state when placing an order failed: useFormGql will now set root error on the form when there is an error response on the GraphQL operation, an error is thrown in onBeforeSubmit and in onSuccess. (@paales)

@graphcommerce/[email protected]

Patch Changes

• 9ba1817 - Solve issue where the filtered pages would throw an error because null object types were forwarded. (@paales)

December 23, 2024 (canary)

@graphcommerce/[email protected]

Patch Changes

• 7d5e75e - Solve issue where the Component prop would we forwarded tot the DOM element of the PaymentMethodActionCard (@paales)

• 058b7bf - Support Magento 2.4.7 placeOrder.errors field to handle possible errors while placing the order. An assertOrderPlaced method was created to assert a valid placed order. (@paales)

@graphcommerce/[email protected]

Patch Changes

• 30d769e - Make sure we are toggling the selected shipping method when a user selects a previously selected shipping method (@paales)

@graphcommerce/[email protected]

Patch Changes

• 6b28b60 - Make sure we are correctly selecting the shipping method form when a user selects a previously selected method again. (@paales)

@graphcommerce/[email protected]

Patch Changes

• 058b7bf - Support Magento 2.4.7 placeOrder.errors field to handle possible errors while placing the order. An assertOrderPlaced method was created to assert a valid placed order. (@paales)

@graphcommerce/[email protected]

Patch Changes

• dc70489 - Support Magento 2.4.7 placeOrder.errors field when placing a Mollie order (@paales)

@graphcommerce/[email protected]

Patch Changes

• c40c559 - Solve an issue where the payment submission would remain in a spinning state when placing an order failed: useFormGql will now set root error on the form when there is an error response on the GraphQL operation, an error is thrown in onBeforeSubmit and in onSuccess. (@paales)

@graphcommerce/[email protected]

Patch Changes

• 9ba1817 - Solve issue where the filtered pages would throw an error because null object types were forwarded. (@paales)

GraphCommerce 9.0.1

See 9.0.0 for full release notes

@graphcommerce/[email protected]

Patch Changes

• #2461 7017b60 - Solve issue with documentation parsing markdown files as mdx (@paales)

• #2454 0f5267b - Update VSCode guide reference (@emmanuel-ferdman)

@graphcommerce/[email protected]

Patch Changes

• #2459 298cb68 - Refactor AddressFields component to spread props correctly for child components. (@carlocarels90)

@graphcommerce/[email protected]

Patch Changes

• #2461 aac4864 - Solve issue where the item.filters would sometimes be invalid (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2461 838fe30 - Solve issue where the preview mode wouldn't initialize if the hygraphLocales weren't defined (@paales)

• #2461 68f2861 - Support for new asset system of Hygraph (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2461 fbe78be - Solve issue where the cart item edit form wasn't aligned in the middle (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2461 3066a2f - When a Customer deselected their shipping address, but had a shipping note filled in it would try to submit the form causing an error. By making the customer_address_id field required we prevent this. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2462 6031bba - fix issue where CategoryChildren would cause layout to break on mobile (@FrankHarland)

• #2461 ff0009b - Solve an issue where CategoryChildren wouldn't be rendered on mobile when using the ProductListLayoutSidebar component. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2461 c83aad6 - Prevent forwarding the isBack prop to the DOM element (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2461 24c68c1 - Solve issue with the SearchField throwing an error in production. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2458 9b33eac - Fix Magento store code not getting set in context.headers.store (@bramvanderholst)

@graphcommerce/[email protected]

Patch Changes

• #2463 db3e142 - Fix issue where layout title would be left aligned (@FrankHarland)

@graphcommerce/[email protected]

Patch Changes

• #2461 fbe78be - Solve issue where the cart item edit form wasn't aligned in the middle (@paales)

• #2456 d742381 - Cleaned up CHANGELOG.md files and generated release notes (@paales)