@graphcommerce/docs 7.1.0-canary.9 → 8.0.0-canary.40

package/CHANGELOG.md

@@ -1,5 +1,79 @@
 # Change Log
 
+## 8.0.0-canary.40
+
+## 7.1.0-canary.39
+
+## 7.1.0-canary.38
+
+## 7.1.0-canary.37
+
+### Patch Changes
+
+- [#2112](https://github.com/graphcommerce-org/graphcommerce/pull/2112) [`15a203737`](https://github.com/graphcommerce-org/graphcommerce/commit/15a2037372cd615602d3e2f3deedba9766fc172c) - Make the "Search" string translatable and fix typo. ([@carlocarels90](https://github.com/carlocarels90))
+
+## 7.1.0-canary.36
+
+## 7.1.0-canary.35
+
+## 7.1.0-canary.34
+
+## 7.1.0-canary.33
+
+## 7.1.0-canary.32
+
+## 7.1.0-canary.31
+
+### Minor Changes
+
+- [#2106](https://github.com/graphcommerce-org/graphcommerce/pull/2106) [`9f8c3cac2`](https://github.com/graphcommerce-org/graphcommerce/commit/9f8c3cac214006315055f37cf8d4a783eb99a7ec) - Split off Magento known issues to separate page ([@hnsr](https://github.com/hnsr))
+
+## 7.1.0-canary.30
+
+## 7.1.0-canary.29
+
+### Patch Changes
+
+- [#2104](https://github.com/graphcommerce-org/graphcommerce/pull/2104) [`d0f1f5a2d`](https://github.com/graphcommerce-org/graphcommerce/commit/d0f1f5a2d1380d1c3931e23218924d5e8b1fc60d) - Document workaround/patch for broken cart error handling with Magento 2.4.6. ([@hnsr](https://github.com/hnsr))
+
+## 7.1.0-canary.28
+
+## 7.1.0-canary.27
+
+## 7.1.0-canary.26
+
+## 7.1.0-canary.25
+
+## 7.1.0-canary.24
+
+## 7.1.0-canary.23
+
+## 7.1.0-canary.22
+
+## 7.1.0-canary.21
+
+## 7.1.0-canary.20
+
+## 7.1.0-canary.19
+
+## 7.1.0-canary.18
+
+## 7.1.0-canary.17
+
+## 7.1.0-canary.16
+
+## 7.1.0-canary.15
+
+## 7.1.0-canary.14
+
+## 7.1.0-canary.13
+
+## 7.1.0-canary.12
+
+## 7.1.0-canary.11
+
+## 7.1.0-canary.10
+
 ## 7.1.0-canary.9
 
 ## 7.1.0-canary.8

package/contributing.md

@@ -7,7 +7,7 @@ process easy and effective for everyone involved.
 
 ### Bug reports
 
-Well-written, thorough bug reports are a great way to contribute to the project.
+Well-written, through bug reports are a great way to contribute to the project.
 Before raising a new issue, please check our
 [issues list ↗](https://github.com/graphcommerce-org/graphcommerce/issues) to
 determine whether the issue you encountered has already been reported.

package/framework/config.md

@@ -77,7 +77,7 @@ Below is a list of all possible configurations that can be set by GraphCommerce.
 
 ### GraphCommerceConfig
 
-#### `canonicalBaseUrl: String!`
+#### canonicalBaseUrl: string (required)
 
 The canonical base URL is used for SEO purposes.
 
@@ -86,7 +86,7 @@ Examples:
 - https://example.com/en
 - https://example.com/en-US
 
-#### `hygraphEndpoint: String!`
+#### hygraphEndpoint: string (required)
 
 The HyGraph endpoint.
 
@@ -94,33 +94,33 @@ The HyGraph endpoint.
 
 Project settings -> API Access -> High Performance Read-only Content API
 
-#### `magentoEndpoint: String!`
+#### magentoEndpoint: string (required)
 
 GraphQL Magento endpoint.
 
 Examples:
 - https://magento2.test/graphql
 
-#### `storefront: [[GraphCommerceStorefrontConfig](#GraphCommerceStorefrontConfig)!]!`
+#### storefront: [GraphCommerceStorefrontConfig](#GraphCommerceStorefrontConfig)[] (required)
 
 All storefront configuration for the project
 
-#### `cartDisplayPricesInclTax: Boolean`
+#### cartDisplayPricesInclTax: boolean
 
 Due to a limitation of the GraphQL API it is not possible to determine if a cart should be displayed including or excluding tax.
 
 When Magento's StoreConfig adds this value, this can be replaced.
 
-#### `compare: Boolean`
+#### compare: boolean
 
 Use compare functionality
 
-#### `compareVariant: [CompareVariant](#CompareVariant) (default: ICON)`
+#### compareVariant: 'CHECKBOX' | 'ICON' = 'ICON'
 
 By default the compare feature is denoted with a 'compare ICON' (2 arrows facing one another).
 This may be fine for experienced users, but for more clarity it's also possible to present the compare feature as a CHECKBOX accompanied by the 'Compare' label
 
-#### `configurableVariantForSimple: Boolean (default: [object Object])`
+#### configurableVariantForSimple: boolean = false
 
 If a simple product is part of a Configurable product page, should the simple product be
 rendered as a configured option of the configurable product page?
@@ -133,25 +133,25 @@ Magento also returns the Simple product and the Configurable product the simple
 If that is the case we render the configurable product page instead of the simple product page but
 the options to select the simple product are pre-selected.
 
-#### `configurableVariantValues: [MagentoConfigurableVariantValues](#MagentoConfigurableVariantValues) (default: [object Object])`
+#### configurableVariantValues: [MagentoConfigurableVariantValues](#MagentoConfigurableVariantValues) = { content: true, url: true }
 
 When a user selects a variant, it will switch the values on the configurable page with the values of the configured variant.
 
 Enabling options here will allow switching of those variants.
 
-#### `crossSellsHideCartItems: Boolean (default: [object Object])`
+#### crossSellsHideCartItems: boolean = false
 
 Determines if cross sell items should be shown when the user already has the product in their cart. This will result in a product will popping off the screen when you add it to the cart.
 
 Default: 'false'
 
-#### `crossSellsRedirectItems: Boolean (default: [object Object])`
+#### crossSellsRedirectItems: boolean = false
 
 Determines if, after adding a cross-sell item to the cart, the user should be redirected to the cross-sell items of the product they just added.
 
 Default: 'false'
 
-#### `customerRequireEmailConfirmation: Boolean`
+#### customerRequireEmailConfirmation: boolean
 
 Due to a limitation in the GraphQL API of Magento 2, we need to know if the
 customer requires email confirmation.
@@ -159,11 +159,11 @@ customer requires email confirmation.
 This value should match Magento 2's configuration value for
 `customer/create_account/confirm` and should be removed once we can query
 
-#### `debug: [GraphCommerceDebugConfig](#GraphCommerceDebugConfig)`
+#### debug: [GraphCommerceDebugConfig](#GraphCommerceDebugConfig)
 
 Debug configuration for GraphCommerce
 
-#### `demoMode: Boolean (default: true)`
+#### demoMode: boolean = true
 
 Enables some demo specific code that is probably not useful for a project:
 
@@ -171,7 +171,7 @@ Enables some demo specific code that is probably not useful for a project:
 - Adds "dominant_color" attribute swatches to the product list items.
 - Creates a big list items in the product list.
 
-#### `googleAnalyticsId: String`
+#### googleAnalyticsId: string
 
 See https://support.google.com/analytics/answer/9539598?hl=en
 
@@ -179,7 +179,7 @@ Provide a value to enable Google Analytics for your store.
 
 To override the value for a specific locale, configure in i18n config.
 
-#### `googleRecaptchaKey: String`
+#### googleRecaptchaKey: string
 
 Google reCAPTCHA site key.
 When using reCAPTCHA, this value is required, even if you are configuring different values for each locale.
@@ -189,17 +189,17 @@ Get a site key and a secret key from https://developers.google.com/recaptcha/doc
 The secret key should be added in the Magento admin panel (Stores > Configuration > Security > Google ReCAPTCHA Storefront > reCAPTCHA v3 Invisible)
 ReCAPTCHA can then be enabled/disabled for the different forms, separately (Stores > Configuration > Security > Google ReCAPTCHA Storefront > Storefront)
 
-#### `googleTagmanagerId: String`
+#### googleTagmanagerId: string
 
 The Google Tagmanager ID to be used on the site.
 
 This value is required even if you are configuring different values for each locale.
 
-#### `hygraphProjectId: String`
+#### hygraphProjectId: string
 
 Hygraph Project ID. **Only used for migrations.**
 
-#### `hygraphWriteAccessEndpoint: String`
+#### hygraphWriteAccessEndpoint: string
 
 Content API. **Only used for migrations.**
 
@@ -207,7 +207,7 @@ Content API. **Only used for migrations.**
 
 Project settings -> API Access -> Content API
 
-#### `hygraphWriteAccessToken: String`
+#### hygraphWriteAccessToken: string
 
 Hygraph Management SDK Authorization Token. **Only used for migrations.**
 
@@ -239,7 +239,7 @@ GC_HYGRAPH_WRITE_ACCESS_TOKEN="AccessTokenFromHygraph"
 yarn graphcommerce hygraph-migrate
 ```
 
-#### `legacyProductRoute: Boolean`
+#### legacyProductRoute: boolean
 
 On older versions of GraphCommerce products would use a product type specific route.
 
@@ -247,45 +247,49 @@ This should only be set to true if you use the /product/[url] AND /product/confi
 
 @deprecated Will be removed in a future version. [migration](../upgrading/graphcommerce-5-to-6.md#product-routing-changes)
 
-#### `limitSsg: Boolean`
+#### limitSsg: boolean
 
 Limit the static generation of SSG when building
 
-#### `previewSecret: String`
+#### previewSecret: string
 
 To enable next.js' preview mode, configure the secret you'd like to use.
 
-#### `productFiltersLayout: [ProductFiltersLayout](#ProductFiltersLayout) (default: DEFAULT)`
+#### productFiltersLayout: 'DEFAULT' | 'SIDEBAR' = 'DEFAULT'
 
 Layout how the filters are rendered.
 DEFAULT: Will be rendered as horzontal chips on desktop and mobile
 SIDEBAR: Will be rendered as a sidebar on desktop and horizontal chips on mobile
 
-#### `productFiltersPro: Boolean`
+#### productFiltersPro: boolean
 
 Product filters with better UI for mobile and desktop.
 
-#### `productRoute: String`
+#### productRoute: string
 
 By default we route products to /p/[url] but you can change this to /product/[url] if you wish.
 
 Default: '/p/'
 Example: '/product/'
 
-#### `robotsAllow: Boolean`
+#### recentlyViewedProducts: [RecentlyViewedProductsConfig](#RecentlyViewedProductsConfig)
+
+Settings for recently viewed products
+
+#### robotsAllow: boolean
 
 Allow the site to be indexed by search engines.
 If false, the robots.txt file will be set to disallow all.
 
-#### `wishlistHideForGuests: Boolean`
+#### sidebarGallery: [SidebarGalleryConfig](#SidebarGalleryConfig)
 
-Hide the wishlist functionality for guests.
+Configuration for the SidebarGallery component
 
-#### `wishlistIgnoreProductWishlistStatus: Boolean`
+#### wishlistHideForGuests: boolean
 
-Ignores whether a product is already in the wishlist, makes the toggle an add only.
+Hide the wishlist functionality for guests.
 
-#### `wishlistShowFeedbackMessage: Boolean`
+#### wishlistShowFeedbackMessage: boolean
 
 Show a message when the product is added to the wishlist.
 
@@ -293,18 +297,18 @@ Show a message when the product is added to the wishlist.
 
 Debug configuration for GraphCommerce
 
-#### `pluginStatus: Boolean`
+#### pluginStatus: boolean
 
 Reports which plugins are enabled or disabled.
 
-#### `webpackCircularDependencyPlugin: Boolean`
+#### webpackCircularDependencyPlugin: boolean
 
 Cyclic dependencies can cause memory issues and other strange bugs.
 This plugin will warn you when it detects a cyclic dependency.
 
 When running into memory issues, it can be useful to enable this plugin.
 
-#### `webpackDuplicatesPlugin: Boolean`
+#### webpackDuplicatesPlugin: boolean
 
 When updating packages it can happen that the same package is included with different versions in the same project.
 
@@ -316,11 +320,11 @@ Issues that this can cause are:
 
 All storefront configuration for the project
 
-#### `locale: String!`
+#### locale: string (required)
 
 Must be a locale string https://www.unicode.org/reports/tr35/tr35-59/tr35.html#Identifiers
 
-#### `magentoStoreCode: String!`
+#### magentoStoreCode: string (required)
 
 Magento store code.
 
@@ -331,7 +335,7 @@ Examples:
 - en-us
 - b2b-us
 
-#### `canonicalBaseUrl: String`
+#### canonicalBaseUrl: string
 
 The canonical base URL is used for SEO purposes.
 
@@ -340,39 +344,39 @@ Examples:
 - https://example.com/en
 - https://example.com/en-US
 
-#### `cartDisplayPricesInclTax: Boolean`
+#### cartDisplayPricesInclTax: boolean
 
 Due to a limitation of the GraphQL API it is not possible to determine if a cart should be displayed including or excluding tax.
 
-#### `defaultLocale: Boolean`
+#### defaultLocale: boolean
 
 There can only be one entry with defaultLocale set to true.
 - If there are more, the first one is used.
 - If there is none, the first entry is used.
 
-#### `domain: String`
+#### domain: string
 
 Domain configuration, must be a domain https://tools.ietf.org/html/rfc3986
 
-#### `googleAnalyticsId: String`
+#### googleAnalyticsId: string
 
 Configure different Google Analytics IDs for different locales.
 
 To disable for a specific locale, set the value to null.
 
-#### `googleRecaptchaKey: String`
+#### googleRecaptchaKey: string
 
 Locale specific google reCAPTCHA key.
 
-#### `googleTagmanagerId: String`
+#### googleTagmanagerId: string
 
 The Google Tagmanager ID to be used per locale.
 
-#### `hygraphLocales: [String!]`
+#### hygraphLocales: string[]
 
 Add a gcms-locales header to make sure queries return in a certain language, can be an array to define fallbacks.
 
-#### `linguiLocale: String`
+#### linguiLocale: string
 
 Specify a custom locale for to load translations.
 
@@ -380,17 +384,37 @@ Specify a custom locale for to load translations.
 
 Options to configure which values will be replaced when a variant is selected on the product page.
 
-#### `content: Boolean`
+#### content: boolean
 
 Use the name, description, short description and meta data from the configured variant
 
-#### `gallery: Boolean`
+#### gallery: boolean
 
 This option enables the automatic update of product gallery images on the product page when a variant is selected,
 provided that the gallery images for the selected variant differ from the currently displayed images.
 
-#### `url: Boolean`
+#### url: boolean
 
 When a variant is selected the URL of the product will be changed in the address bar.
 
-This only happens when the actual variant is can be accessed by the URL.
+This only happens when the actual variant is can be accessed by the URL.
+
+### RecentlyViewedProductsConfig
+
+Settings for recently viewed products
+
+#### enabled: boolean
+
+Enable/disable recently viewed products
+
+#### maxCount: number
+
+Number of recently viewed products to be stored in localStorage
+
+### SidebarGalleryConfig
+
+SidebarGalleryConfig will contain all configuration values for the Sidebar Gallery component.
+
+#### paginationVariant: 'DOTS' | 'THUMBNAILS_BOTTOM'
+
+Variant used for the pagination

package/framework/plugins-react.md

@@ -37,7 +37,7 @@ Function plugins, which can be used to:
 
 In this example we're going to add some text to list items, just like the text
 ‘BY GC’ that can seen in the demo on
-[category pages](https://graphcommerce.vercel.app/nl/women/business).
+[category pages](https://graphcommerce.vercel.app/en/women/business).
 
 1. Create a new file in `/plugins/ProductListItemByGC.tsx` with the following
    contents:

package/magento/known-issues.md

@@ -0,0 +1,54 @@
+---
+menu: Known issues
+---
+
+# Known issues
+
+An overview of bugs and limitations you may run into with Magento's GraphQL API:
+
+## Cart-related mutations result in `Can not find cart with ID` or `Cart isn't active` errors
+
+Affected Magento versions:
+
+- `2.4.7`: only `2.4.7-beta1`
+- `2.4.6`: all versions
+
+This is caused by a regression which results in some GraphQL errors no longer
+getting a category extension string (such as `graphql-no-such-entity`).
+Normally, these errors are handling by automatically creating a new cart, but
+without the proper error category this error-handling logic is nog triggered.
+
+As a workaround, you can apply
+[cart-error-category.patch](./patches/cart-error-category.patch).
+
+See also
+https://github.com/magento/magento2/commit/49cbe774020d3dfa6ee2b8702376a947801c9971
+
+## Customer is forced to sign up, even if already registered
+
+Affected Magento versions:
+
+- `2.4.7` and all future release series
+- `2.4.6`: `2.4.6-p1` and up
+- `2.4.5`: `2.4.5-p3` and up
+- `2.4.4`: `2.4.4-p4` and up
+
+During customer login, GraphCommerce queries Magento to determine whether the
+customer account already exists or not. If not, the sign-up form is shown
+instead.
+
+In affected Magento versions, the behavior of the `isEmailAvailable` query that
+is used to do this was made dependent on the `Enable Guest Checkout Login`
+configuration setting. If disabled, this query will always return `true`,
+resulting in the sign-up form always being shown, even if the customer already
+exists.
+
+To solve this, the following setting must be set to `Yes`:
+`Stores -> Configuration -> Sales -> Checkout -> Checkout Options -> Enable Guest Checkout Login`
+
+See also
+https://developer.adobe.com/commerce/php/development/backward-incompatible-changes/highlights/#isemailavailable-api
+
+## Next steps
+
+- [Overview](./readme)

package/magento/patches/cart-error-category.patch

@@ -0,0 +1,46 @@
+Fix inactive/non-existent cart handling by re-adding GraphQL error category extension
+
+@package magento/framework
+
+Index: GraphQl/Exception/GraphQlNoSuchEntityException.php
+IDEA additional info:
+Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
+<+>UTF-8
+===================================================================
+diff --git a/GraphQl/Exception/GraphQlNoSuchEntityException.php b/GraphQl/Exception/GraphQlNoSuchEntityException.php
+--- a/GraphQl/Exception/GraphQlNoSuchEntityException.php
++++ b/GraphQl/Exception/GraphQlNoSuchEntityException.php	(date 1698390008711)
+@@ -7,6 +7,8 @@
+
+ namespace Magento\Framework\GraphQl\Exception;
+
++use GraphQL\Error\ClientAware;
++use GraphQL\Error\ProvidesExtensions;
+ use Magento\Framework\Exception\NoSuchEntityException;
+ use Magento\Framework\Phrase;
+
+@@ -15,7 +17,7 @@
+  *
+  * @api
+  */
+-class GraphQlNoSuchEntityException extends NoSuchEntityException implements \GraphQL\Error\ClientAware
++class GraphQlNoSuchEntityException extends NoSuchEntityException implements ClientAware, ProvidesExtensions
+ {
+     const EXCEPTION_CATEGORY = 'graphql-no-such-entity';
+
+@@ -53,4 +55,15 @@
+     {
+         return self::EXCEPTION_CATEGORY;
+     }
++
++    /**
++     * Get error category
++     *
++     * @return array
++     */
++    public function getExtensions(): array
++    {
++        $exceptionCategory['category'] = $this->getCategory();
++        return $exceptionCategory;
++    }
+ }

package/magento/readme.md

@@ -7,6 +7,12 @@ menu: Overview
 To integrate with Magento, most of the functionality should work out-of-the box
 if Magento exposes a working GraphQL API.
 
+Some additional configuration may be required, which is documented below.
+
+Currently, the GraphQL API also has some bugs and limitations which in some
+cases requires a patch to work around, please see
+[Known issues](./known-issues.md)
+
 ## Magento configuration
 
 ### Configure Base Link Url to get emails working
@@ -64,16 +70,6 @@ Remove the URL suffixes from products and categories. (default is `.html`)
 `Stores -> Configuration -> Catalog -> Catalog -> Search Engine Optimization -> Product URL Suffix`
 `Stores -> Configuration -> Catalog -> Catalog -> Search Engine Optimization -> Category URL Suffix`
 
-### Enable guest checkout login
-
-During customer login, GraphCommerce queries Magento to determine whether the
-customer account already exists. To do this the following setting must be set to
-Yes:
-`Stores -> Configuration -> Sales -> Checkout -> Checkout Options -> Enable Guest Checkout Login`
-
-If this is not set correctly, customers will not be able to log in, since they
-will always be prompted to create a new account.
-
 ## Optional packages
 
 - [Store Pickup / MSI](https://github.com/graphcommerce-org/graphcommerce/tree/main/packages/magento-cart-pickup)
@@ -92,3 +88,4 @@ will always be prompted to create a new account.
 
 - [Full feature list](../feature-list.md)
 - [SEO Migration](./seo-migration.md)
+- [Known issues](./known-issues.md)

package/package.json

@@ -2,10 +2,10 @@
   "name": "@graphcommerce/docs",
   "homepage": "https://www.graphcommerce.org/docs",
   "repository": "github:graphcommerce-org/graphcommerce/docs",
-  "version": "7.1.0-canary.9",
+  "version": "8.0.0-canary.40",
   "sideEffects": true,
-  "devDependencies": {
-    "@graphcommerce/prettier-config-pwa": "7.1.0-canary.9"
+  "peerDependencies": {
+    "@graphcommerce/prettier-config-pwa": "8.0.0-canary.40"
   },
   "prettier": "@graphcommerce/prettier-config-pwa"
 }