GraphQL: New mutations for managing customers

[keharper]

Purpose of this pull request

This pull request (PR) adds documentation for the createCustomerV2, updateCustomerV2, and updateCustomerPassword mutations. The createCustomer and updateCustomer mutations have been deprecated.

Code PR: magento/magento2#28888
Code issue: magento/magento2#28570

Affected DevDocs pages

• guides/v2.4/graphql/mutations/create-customer-v2.html
• guides/v2.4/graphql/mutations/update-customer-v2.html
• guides/v2.4/graphql/mutations/update-customer-email.html

Links to Magento source code

• ...

whatsnew
We have added the createCustomerV2 and updateCustomerV2 mutations to manage customer accounts. These new mutations require different input objects than the createCustomer and updateCustomer mutations. To change a customer's email address, use the new updateCustomerEmail mutation.

[erikmarr]

Looks good. Just a minor question.

[cpartica]

did you leave on purpose all possible customer fields?
I guess yes because it's an example
maybe add a comment in the example # client can add other optional fields in the query
you can add comments wtih # in any graphql query

[keharper]

They're just examples, not meant to show every possibility. Keeping the examples to typical and/or minimal use cases also helps maintain these examples, as I don't have to update the example each time an attribute is added.

Dismissing review because requests aren't currently feasible.

[keharper]

running tests

[ghost]

Hi @keharper, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.