GraphQL Schema for createCustomer does not match validation requirements

[magento-engcom-team]

The schema for the createCustomer mutation shows the input object as a whole as required but it does not show the individual required fields. For example, I tried to make an account passing ONLY the email and password but received an error after submission that said first name and last name were required.

https://i.gyazo.com/baffd808d33594f6aa1f9ef785cac540.png

After checking the schema, it does not look like any of the props within the input object are listed as required. Fixing the schema will help catch errors ahead of time and during development of features.

https://i.gyazo.com/47babb76479f71ee87e5e46051c9b42e.png

[m2-assistant]

Hi @magento-engcom-team. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[michalderlatka]

@magento I am working on this

[m2-assistant]

Hi @michalderlatka! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[michalderlatka]

@magento I am working on this

[m2-assistant]

Hi @cpartica. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
     Details

     If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

Hi @magento-engcom-team. Thank you for your report.
The issue has been fixed in #28888 by @michalderlatka in 2.4-develop branch
Related commit(s):

• 1943018094edcedddc73463a5e703a9a76653ad8
• 887f19109e9ecac0c15af7f2ddbbbf9ec7d360b3
• b5208cd5800bcdf14644c65847ecb4781e05ef8a
• 0f7d805b24f35a8c9650b1fa61e6048d14fd7a27
• 592f5de3a50cd80fe26a1c40534de9b92516a927
• 3a4cfa1fd0a05e040875ff51afe1d74a124fe211
• 2e77e2292e15588086ba4358798be2185a68c44c

The fix will be available with the upcoming 2.4.1 release.