@graphcommerce/docs 7.1.0-canary.52 → 7.1.0-canary.54

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Change Log
 
+## 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

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/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.52",
+  "version": "7.1.0-canary.54",
   "sideEffects": true,
   "peerDependencies": {
-    "@graphcommerce/prettier-config-pwa": "^7.1.0-canary.52"
+    "@graphcommerce/prettier-config-pwa": "^7.1.0-canary.54"
   },
   "prettier": "@graphcommerce/prettier-config-pwa"
 }