asyavee/medusa-store
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: added a note about running migrations (#2875)

Browse Source 
* docs: added a note about running migrations

* docs: fixed link
This commit is contained in:
Shahed Nasser
2022-12-22 12:12:21 +02:00
committed by GitHub
parent 7c0ae7f6ba
commit f4c9a4698f
2 changed files with 19 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/content/advanced/backend/upgrade-guides/1-7-0.md
View File

@@ -10,8 +10,20 @@ Version `1.7.0` of Medusa introduces a breaking change in the [CustomerService](
In this new version, the method [`retrieveByEmail` in the Customer Service](../../../references/services/classes/CustomerService.md#retrievebyemail) has been deprecated in favor of other methods. Read the actions required below to learn which methods to use instead.
In addition, after introducing the Claim Order feature, this version of Medusa introduces changes in the database that allows two customers having the same email based on the value of the `has_account` field. This change requires running migrations after the update.
## Actions Required
### Run Migrations
Run the following command to run migrations:
```bash
medusa migrations run
```
### Change Used Methods
Instead of using `customerService.retrieveByEmail`, you should now use the methods `customerService.retrieveRegisteredByEmail` or `customerService.retrieveUnRegisteredByEmail`.
The `customerService.retrieveRegisteredByEmail` method allows you to retrieve a registered customer by email:

8
docs/content/advanced/storefront/implement-claim-order.mdx
View File

@@ -5,11 +5,17 @@ import TabItem from '@theme/TabItem';
In this document, you’ll learn how to implement the claim order flow in a storefront to allow customers to claim their orders.
:::note
This flow was added starting from Medusa v1.7. You can learn more about upgrading in the [upgrade guide](../backend/upgrade-guides/1-7-0.md).
:::
## Flow Overview
When a guest customer places an order, their order is not associated with any customer. The order is only associated with an email that the guest customer provides during checkout.
This email must be an email that isn’t used with an existing account. Also, this email cannot be used later on to create a new account. It can, however, be used to create another order as a guest customer.
This email must be an email that isn’t used with an existing account. It can, however, be used to create another order as a guest customer.
After this customer registers with a different email and logs in, they can claim their order by providing the order’s ID. An email will then be sent to the email address associated with the order.