Releases: graphcommerce-org/graphcommerce
Release 10.1.0-canary.9
@graphcommerce/magento-payment-multisafepay@10.1.0-canary.9
Patch Changes
- #2583
01bb1df- Fixed a bug in MSPPaymentHandler where successful MultiSafepay payments were prevented from redirecting to the success page due to an incorrect condition in the payment handler. (@Giovanni-Schroevers)
Release 10.1.0-canary.7
@graphcommerce/next-ui@10.1.0-canary.7
Patch Changes
- #2610
7b6ba3f- Fix duplicate React key warning in<NumberFormat>/<CurrencyFormat>/<Money>for numbers with a thousands group separator.Intl.NumberFormat.formatToParts()emits multiple parts withtype: "integer"(one per group, e.g.1.234,56produces twointegerparts). Usingkey={part.type}therefore collided. Switched to an index key — parts are already wrapped insuppressHydrationWarning, so SSR/client divergence isn't an issue. (@paales)
Release 10.1.0-canary.6
@graphcommerce/storyblok-ui@10.1.0-canary.6
Patch Changes
-
#2609
fe29527- Drop@graphcommerce/magento-cmsfrom the Storyblok example, ship locale-redirect proxy withstoryblok-uiThe Storyblok example had several leftovers from a half-completed migration off Magento CMS, all conceptually out of place in an example whose purpose is "all content lives in Storyblok":
pages/page/[...url].tsx— a CMS page handler whosegetStaticPathscalledgetCategoryStaticPaths(returns Magento category URLs). Feeding category URLs into thecmsPagequery causedgetStaticPropsto return aredirect, which Next.js rejects during prerender — crashingnext build.Layout.graphqlqueriedcmsBlocks(["footer_links_block"])but the resulting prop was destructured-and-discarded in both layout components — the Footer is fully driven by Storyblok'sglobalConfig. The dead query also produced noisy GraphQL errors at build time on backends without the block.pages/404.tsxrendered a Magentocms_no_routeCMS page (with a hardcoded fallback if absent).proxy.tswas a hand-written file with hardcodedLOCALES = ['en', 'nl']— broken for any other storefront combination, and not using the plugin system.
This PR:
- Removes
pages/page/[...url].tsx, the deadcmsBlocksquery and unused destructures, the Magento CMS fallback inpages/404.tsx, and the@graphcommerce/magento-cmsdependency - Migrates
proxy.ts→ standard managed re-export - Adds
@graphcommerce/storyblok-ui/plugins/LocaleRedirectProxy.tswithifConfig: 'storyblok'— every project depending on@graphcommerce/storyblok-uinow gets locale-redirect (Visual Editor_storyblok_lang+ Accept-Language root) automatically, with locales read fromstorefrontconfig
If a project needs Magento CMS pages alongside Storyblok, it can re-add the dependency and a route — but the example should default to pure Storyblok. (@paales)
Release 10.1.0-canary.5
chore(release): update prerelease versions
Release 10.1.0-canary.4
@graphcommerce/storyblok-ui@10.1.0-canary.4
Patch Changes
-
#2606
d30c568- Performance improvements for Storyblok bridge (@bramvanderholst) -
#2606
d30c568- Added Storyblok pages to content sitemap (@bramvanderholst)
Release 10.0.4-canary.1
@graphcommerce/ecommerce-ui@10.0.4-canary.1
Patch Changes
- #2585
c9e862a- Get redirectTo from the url params instead of the headers (@Giovanni-Schroevers)
Release 10.0.4-canary.0
@graphcommerce/magento-search-overlay@10.0.4-canary.0
Patch Changes
-
#2580
c406bbd- Use immediate input value for Enter navigation.Modified SearchOverlayProvider to pull the search query directly from the event target during the Enter key event. This prevents the "partial query" bug caused by navigating with the lagging debounced state. (@Giovanni-Schroevers)
Release 10.0.3
@graphcommerce/next-config@10.0.3
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/next-config@10.0.3-canary.0
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)