Skip to content
This repository has been archived by the owner on Dec 19, 2019. It is now read-only.

[Mutations] My Account > Change account information #55

Closed
misha-kotov opened this issue May 22, 2018 · 2 comments
Closed

[Mutations] My Account > Change account information #55

misha-kotov opened this issue May 22, 2018 · 2 comments
Assignees
Labels

Comments

@misha-kotov
Copy link

misha-kotov commented May 22, 2018

As a Magento developer, I need to build a functional My Account experience for customers via GraphQL so that I can build basic ecommerce experiences for shoppers on the front-end using only GraphQL.

GraphQL needs to provide sufficient mutations (ways to create/update/delete data) for a developer to build out the storefront My Account experience for a shopper.

Use cases:

  • A logged-in shopper can change their account information from the My Account Page

Acceptance criteria:

  • GraphQL provides a mutation through which the current logged-in shopper can change their account information
  • Authentication is handled through a session cookie (changing the email address requires that current password is provided)
  • A guest shopper cannot change the account information for any user
  • A meaningful error message is given if current password is incorrect or if entered data does not conform to requirements
  • List of fields that can be changed:
    • First Name
    • Last Name
    • Email address (requires current password)
  • Changes are covered with web API functional tests. See \Magento\GraphQl\Catalog\ProductViewTest::testQueryAllFieldsSimpleProduct as an example.
  • Please propose GraphQL schema before starting implementation

My Account area impacted:

  • Account Information tab

Note: will likely merge #56 into this story

@misha-kotov misha-kotov added for-grooming This issue needs to be discussed before it can be worked on additional-coverage labels May 22, 2018
@paliarush paliarush removed the for-grooming This issue needs to be discussed before it can be worked on label Jul 31, 2018
@nuzil nuzil self-assigned this Jul 31, 2018
@nuzil
Copy link
Contributor

nuzil commented Aug 15, 2018

As example of schema:

mutation {
  customerUpdate(
    firstname: "NAME",
    lastname: "LastNAME",
    email:"E-Mail"
    password: "password if required"
  ){
    firstname
    lastname
    email
  }
}

magento-engcom-team pushed a commit that referenced this issue Aug 17, 2018
MAGETWO-91620: It is not possible to use function setInAllAttributeSe…
@naydav
Copy link
Contributor

naydav commented Nov 20, 2018

#162

@naydav naydav closed this as completed Nov 20, 2018
@naydav naydav added the 2.3.1 label Dec 7, 2018
@naydav naydav added this to the Release: 2.3.1 milestone Dec 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants