@graphcommerce/docs 8.0.0-canary.40 → 8.0.0-canary.69

package/CHANGELOG.md

@@ -1,8 +1,58 @@
 # Change Log
 
-## 8.0.0-canary.40
+## 8.0.0-canary.69
 
-## 7.1.0-canary.39
+## 7.1.0-canary.68
+
+## 7.1.0-canary.67
+
+## 7.1.0-canary.66
+
+## 7.1.0-canary.65
+
+## 7.1.0-canary.64
+
+## 7.1.0-canary.63
+
+## 7.1.0-canary.62
+
+## 7.1.0-canary.61
+
+## 7.1.0-canary.60
+
+## 7.1.0-canary.59
+
+## 7.1.0-canary.58
+
+## 7.1.0-canary.57
+
+## 7.1.0-canary.56
+
+## 7.1.0-canary.55
+
+## 7.1.0-canary.54
+
+## 7.1.0-canary.53
+
+### Patch Changes
+
+- [#2119](https://github.com/graphcommerce-org/graphcommerce/pull/2119) [`6adb2e72e`](https://github.com/graphcommerce-org/graphcommerce/commit/6adb2e72ece8210757ced178779dfba11b1bcf55) - Clarify texts by adding formatting and correcting spelling. ([@carlocarels90](https://github.com/carlocarels90))
+
+## 7.1.0-canary.52
+
+## 7.1.0-canary.51
+
+## 7.1.0-canary.50
+
+## 7.1.0-canary.49
+
+## 7.1.0-canary.48
+
+## 7.1.0-canary.47
+
+## 7.1.0-canary.46
+
+## 7.1.0-canary.45
 
 ## 7.1.0-canary.38
 
@@ -899,31 +949,31 @@
   All occurences of `<Trans>` and `t` need to be replaced:
 
   ```tsx
-  import { Trans, t } from '@lingui/macro'
+  import { Trans, t } from "@lingui/macro";
 
   function MyComponent() {
-    const foo = 'bar'
+    const foo = "bar";
     return (
       <div aria-label={t`Account ${foo}`}>
         <Trans>My Translation {foo}</Trans>
       </div>
-    )
+    );
   }
   ```
 
   Needs to be replaced with:
 
   ```tsx
-  import { Trans } from '@lingui/react'
-  import { i18n } from '@lingui/core'
+  import { Trans } from "@lingui/react";
+  import { i18n } from "@lingui/core";
 
   function MyComponent() {
-    const foo = 'bar'
+    const foo = "bar";
     return (
       <div aria-label={i18n._(/* i18n */ `Account {foo}`, { foo })}>
-        <Trans key='My Translation {foo}' values={{ foo }}></Trans>
+        <Trans key="My Translation {foo}" values={{ foo }}></Trans>
       </div>
-    )
+    );
   }
   ```
 

package/framework/config.md

@@ -171,6 +171,16 @@ 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.
 
+#### enableGuestCheckoutLogin: boolean
+
+Enable Guest Checkout Login:
+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.
+
+For Magento versions, 2.4.7, 2.4.6-p1 and up, 2.4.5-p3 and up, 2.4.4-p4 and up, the following setting must be set to Yes
+
+`Stores -> Configuration -> Sales -> Checkout -> Checkout Options -> Enable Guest Checkout Login`
+
 #### googleAnalyticsId: string
 
 See https://support.google.com/analytics/answer/9539598?hl=en
@@ -301,6 +311,10 @@ Debug configuration for GraphCommerce
 
 Reports which plugins are enabled or disabled.
 
+#### sessions: boolean
+
+Enable debugging interface to debug sessions
+
 #### webpackCircularDependencyPlugin: boolean
 
 Cyclic dependencies can cause memory issues and other strange bugs.

package/hygraph/property-picker.md

@@ -0,0 +1,45 @@
+# Hygraph Dynamic Rows
+
+As you might have learned, Dynamic Rows enable the addition of rows across
+multiple pages through rule-based relationships, rather than manually adding a
+row to each page. These rules hinge on shared attributes among the pages, with a
+category being a typical example of such an attribute. To enable the Dynamic Row
+UI Extension, follow the installation instructions as below.
+
+> Installation
+>
+> [Click here to install the Dynamic Row UI Extension](https://app.hygraph.com/apps/dynamic-row-property-picker/new)
+
+<img width="1792" alt="image" src="https://github.com/graphcommerce-org/graphcommerce/assets/49681263/3226eedb-e58c-4d3f-9516-14ff6ed56f24">
+
+## Enabling the Application
+
+Once you click the link and authorize the application, you'll be taken to the
+app's configuration page. On this page, you can switch the application on or off
+as needed.
+
+<img width="1792" alt="image" src="https://github.com/graphcommerce-org/graphcommerce/assets/49681263/ec9b55f6-14f6-466e-8a31-0b893ffe1297">
+
+## Enabling the field
+
+Now to enable the field, go to your Hygraph schema. Under components you should
+have a `Text` and `Number` component. Each of these have a field with api ID
+`property`. You will have to delete this field in both components. This will
+result in current field data being lost, so in case you are migrating to the
+extended UI, make sure to have a copy of those fields somewhere else. 
+
+> Note
+>
+> Make sure you migrated your schema to Graphcommerce 7.0 with
+> [our Hygraph-CLI.](./cli.md)
+
+Replace the existing fields with the new `Property picker` field in the right sidebar
+(it should be under `Slug` and above `Rich text`). While adding the
+`Property picker` field make sure that you make it `required`.
+
+<img width="1792" alt="image" src="https://github.com/graphcommerce-org/graphcommerce/assets/49681263/9206f86d-477c-4eaf-bec6-1648874bee5e">
+
+## Start building with your new Dynamic Rows UI!
+
+If you have any questions about the feature, please reach out to us in our Slack
+channel.

package/magento/implementing-payment-gateways.md

@@ -23,7 +23,7 @@ There are multiple flows to handle payments.
 
 ### Redirecting payment gateway
 
-The first step is to call setPaymentMethodOnCart and placeOrder.
+The first step is to call `setPaymentMethodOnCart` and `placeOrder`.
 
 ```ts
 const variables = {
@@ -69,14 +69,16 @@ mutation MyGatewayPaymentOptionsAndPlaceOrder($cartId: String!) {
 ```
 
 When the query succeeds the GraphCommerce payment module will redirect to the
-payment_url. The customer handles it's payment on the payment gateway's website.
-One of the following things can happen:
-
-- Result 1: The customer has successfully paid and the customer is redirected
-  back to the `return_url` with the $TOKEN injected.
-- Result 2: The customer has failed their pauyment and the customer is
-  redirected back to the `return_url` with the $TOKEN injected.
-- Result 3: The customer presses back in their browser and we still get the
+`payment_url`. The customer handles it's payment on the payment gateway's
+website. One of the following things can happen:
+
+- **Result 1:** The customer has successfully paid and the customer is
+  redirected back to the `return_url` with the `$TOKEN` injected.
+
+- **Result 2:** The customer has failed their payment and the customer is
+  redirected back to the `return_url` with the `$TOKEN` injected.
+
+- **Result 3:** The customer presses back in their browser and we still get the
   token from the `placeOrder` mutation.
 
 GraphCommerce now needs to check if the payment has indeed succeeded by calling
@@ -95,7 +97,7 @@ mutation MyGatewayProcessPayment($cartId: String!, $token: String!) {
 }
 ```
 
-After that GraphCommerce van either:
+After that GraphCommerce can either:
 
 - Redirect to the success page
 - Restore the cart, show the error message and let the customer checkout again.
@@ -109,18 +111,17 @@ input PaymentMethodInput {
 
 input MyGatewayPaymentInput {
   """
-  The URL to redirect the customer to after the payment has been processed.
+  The URL to which the customer should be redirected, after the payment has been processed.
 
-  This will should be a fully qualified URL: `https://mydomain.com/checkout/payment?token=$TOKEN`
-  $TOKEN will be repaced with the payment gateway token.
+  This should be a fully qualified URL: https://mydomain.com/checkout/payment?token=$TOKEN, where $TOKEN will be replaced with the payment gateway token.
 
-  This information should be stored in the database (encryped if required)
+  This information should be stored in the database (encrypted if required)
   """
   return_url: String!
   """
   Payment gateway can accept any custom field, for example an issuer or any additional information that can be configured in the checkout.
 
-  This information should be stored in the database (encryped if required)
+  This information should be stored in the database (encrypted if required)
   """
   custom_field: String
 }

package/magento/known-issues.md

@@ -24,31 +24,6 @@ As a workaround, you can apply
 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/package.json

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

package/upgrading/graphcommerce-5-to-6.md

@@ -21,9 +21,8 @@ The route for the product has changed from `/product/[url]`,
 `/product/configurable/[url]`, etc. to `/p/[url]` by default. This is a
 singlular product page for all product types.
 
-You can keep using the old behavior by setting
-[legacyProductRoute](../framework/config.md#legacyproductroute-boolean) to true.
-This legacy routing will be removed in a future version.
+~~You can keep using the old behavior by setting `legacyProductRoute` to true.~~
+The legacy routing has been removed in GraphCommerce 8.
 
 You can also change the product route from `/p/[url]` to something else by
 configuring [productRoute](../framework/config.md#productroute-string)

package/upgrading/graphcommerce-7-to-8.md

@@ -0,0 +1,18 @@
+# Upgrading from GraphCommerce 6 to 7
+
+Depending on the amounts of customisations you've made, there are some manual
+steps. Please follow the regular [upgrade steps first](./readme.md).
+
+1. [`legacyProductRoute` is removed](#legacyproductroute-is-removed)
+2. [Upgrading your Hygraph schema](#upgrading-your-hygraph-schema)
+
+## `legacyProductRoute` is removed
+
+🟠 Only required if you've used the legacyProductRoute
+
+Remove all `/pages/product/*` routes.
+
+## Upgrading your Hygraph schema
+
+Upgrade your Hygraph schema with the [Hygraph migration cli](../hygraph/cli.md).
+Select `graphcommerce7to8` as version.