This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Migrating Customer endpoint to new directories as per Magedoc3973 #5124
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
erikmarr
added
Site Improvements
keharper
reviewed
Aug 7, 2019
| ```graphql | ||
| mutation { | ||
| changeCustomerPassword( | ||
| currentPassword: "[email protected]", |
There was a problem hiding this comment.
Suggested change
| currentPassword: "[email protected]", | |
| currentPassword: "[email protected]" |
| mutation { | ||
| updateCustomerAddress(id:3, input: { | ||
| city: "New City" | ||
| postcode: "5555" |
There was a problem hiding this comment.
Suggested change
| postcode: "5555" | |
| postcode: "55555" |
| "updateCustomerAddress": { | ||
| "id": 3, | ||
| "city": "New City", | ||
| "postcode": 5555 |
There was a problem hiding this comment.
Suggested change
| "postcode": 5555 | |
| "postcode": 55555 |
|
|
||
| The `isEmailAvailable` query checks whether the specified email has already been used to create a customer account. A value of `true` indicates the email address is available, and the customer can use the email address to create an account. | ||
|
|
||
| To return or modify information about a customer, Magento recommends you use customer tokens in the header of your GraphQL calls. However, you also can use [session authentication]({{ page.baseurl }}/get-started/authentication/gs-authentication-session.html). |
There was a problem hiding this comment.
I think it's safe to not include this paragraph, because the query is checking whether a specific emall address has been used before.
keharper
reviewed
Aug 15, 2019
keharper
suggested changes
Aug 15, 2019
keharper
approved these changes
Aug 26, 2019
|
running tests |
1 similar comment
|
running tests |
|
running tests |
|
Hi @erikmarr, thank you for your contribution! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
This pull request (PR) moves the customer endpoint to the new queries/mutations subdirs.
Affected DevDocs pages