Release 10.0.3

@graphcommerce/[email protected]

Patch Changes

• fdad2b7 - Added support in component props for Generic components. Solves an issue with creating plugins on the AddressFields component. (@paales)

• fdad2b7 - Fixed issue where additional props on a plugin did not carry to the final component. Now we can extend the original component's props with additional props from plugins. (@paales)

Release 10.0.3-canary.0

@graphcommerce/[email protected]

Patch Changes

• fdad2b7 - Added support in component props for Generic components. Solves an issue with creating plugins on the AddressFields component. (@paales)

• fdad2b7 - Fixed issue where additional props on a plugin did not carry to the final component. Now we can extend the original component's props with additional props from plugins. (@paales)

Release 10.0.2

@graphcommerce/[email protected]

Patch Changes

• aaa79dd - Solve issue where the GuestOrCustomerMask would hide incorrectly (@paales)

@graphcommerce/[email protected]

Patch Changes

• aaa79dd - Do not query the head_includes from the backend as that may never be rendered and might contain big content. (@paales)

Release 10.0.2-canary.0

@graphcommerce/[email protected]

Patch Changes

• aaa79dd - Solve issue where the GuestOrCustomerMask would hide incorrectly (@paales)

@graphcommerce/[email protected]

Patch Changes

• aaa79dd - Do not query the head_includes from the backend as that may never be rendered and might contain big content. (@paales)

Release 10.0.1-canary.5

@graphcommerce/[email protected]

Patch Changes

• 5166a95 - Solve issue where the GuestOrCustomerMask would hide incorrectly (@paales)

@graphcommerce/[email protected]

Patch Changes

• 1cd75c3 - Do not query the head_includes from the backend as that may never be rendered and might contain big content. (@paales)

Release 10.0.1

@graphcommerce/[email protected]

Patch Changes

• #2569 1ba54d4 - Properly handle the new uid stuff (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2568 f1b60ac - Solve issue where the cache wasn't available from the context anymore in @apollo/client@4 now uses the operation.client.cache (@paales)

• #2571 591fb82 - Make sure the default_display_currency_code is always fetched properly for Algolia (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2568 f1b60ac - Solve issue where the cache wasn't available from the context anymore in @apollo/client@4 now uses the operation.client.cache (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2568 6714cbb - Deprecated globalApolloClient (@paales)

• #2571 2350c13 - Show loading skeleton when loading and there is no data, but show when there is an error so we dont get in a stuck state. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2568 71e2bcc - Peer dependency issues (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 78a2a8a - Solve issue where the @client fields could not be resolved correctly. (@paales)

• #2568 f1b60ac - Solve issue where the cache wasn't available from the context anymore in @apollo/client@4 now uses the operation.client.cache (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2568 dc57da4 - Moved from form.watch to useWatch everywhere which works even if the fields are later initialized. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2568 dc57da4 - Moved from form.watch to useWatch everywhere which works even if the fields are later initialized. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2568 dc57da4 - Moved from form.watch to useWatch everywhere which works even if the fields are later initialized. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2568 dc57da4 - Moved from form.watch to useWatch everywhere which works even if the fields are later initialized. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2568 0188c30 - Moved the CmsPage query from the route query to the cmsPage query (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 78a2a8a - Solve issue where the @client fields could not be resolved correctly. (@paales)

• #2568 dc57da4 - Moved from form.watch to useWatch everywhere which works even if the fields are later initialized. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 78a2a8a - Solve issue where the @client fields could not be resolved correctly. (@paales)

• #2568 dc57da4 - Moved from form.watch to useWatch everywhere which works even if the fields are later initialized. (@paales)

• #2571 0146abe - Created a new GuestOrCustomerMask to show information based on their loggedIn state respecting the masking of private content. (@paales)

• #2568 f1b60ac - Solve issue where the cache wasn't available from the context anymore in @apollo/client@4 now uses the operation.client.cache (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 78a2a8a - Solve issue where the @client fields could not be resolved correctly. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2568 ddeaf5d - Solve hydration erorr while loading reviews (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 d9c7545 - When switching stores unset the currency when there is no selection available for a given store. (@paales)

• #2571 6d5ff59 - Do not send an unacceptable store currency due to a configuration error and make sure the correct currency is stored. Show a StoreSwitcherFab on mobile. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2568 16efe30 - Hide ActionCard-end if there is no content (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2574 100cd16 - Forward Step when using assign for the order (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2569 f76edb7 - Fix issue with container sizing of breadcrumb (@paales)

• #2568 6277f34 - Solve issue where reactCompiler was enabled but...

Release 10.0.1-canary.4

@graphcommerce/[email protected]

Patch Changes

• #2576 4d2adec - release again (@paales)

Release 10.0.1-canary.3

@graphcommerce/[email protected]

Patch Changes

• #2574 100cd16 - Forward Step when using assign for the order (@paales)

Release 10.0.1-canary.2

@graphcommerce/[email protected]

Patch Changes

• #2572 acd9973 - Change release (@paales)

Release 10.0.1-canary.1

@graphcommerce/[email protected]

Patch Changes

• #2571 591fb82 - Make sure the default_display_currency_code is always fetched properly for Algolia (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 2350c13 - Show loading skeleton when loading and there is no data, but show when there is an error so we dont get in a stuck state. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 78a2a8a - Solve issue where the @client fields could not be resolved correctly. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 78a2a8a - Solve issue where the @client fields could not be resolved correctly. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 78a2a8a - Solve issue where the @client fields could not be resolved correctly. (@paales)

• #2571 0146abe - Created a new GuestOrCustomerMask to show information based on their loggedIn state respecting the masking of private content. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 78a2a8a - Solve issue where the @client fields could not be resolved correctly. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 d9c7545 - When switching stores unset the currency when there is no selection available for a given store. (@paales)

• #2571 6d5ff59 - Do not send an unacceptable store currency due to a configuration error and make sure the correct currency is stored. Show a StoreSwitcherFab on mobile. (@paales)

@graphcommerce/[email protected]

Patch Changes

• #2571 a16bed1 - Always copy the file if the original file is a core file, allowing overrides. (@paales)