Update Customer mutation allows for invalid shipping input variables

[ardiewen]

Describe the bug

When running the updateCustomer mutation, the allowed shipping input variables include:

email
phone

According to The WC REST API Customer Properties documentation, these are not valid properties of the Shipping object.

To Reproduce
Steps to reproduce the behavior:

1. Create an updateCustomer mutation:

With email input variable:

mutation UPDATE_CUSTOMER {
  updateCustomer(input: {shipping: { email: "test@test.com"}, clientMutationId: "some-set-of-strings"}) {
    clientMutationId
  }
}

Response:

{
  "errors": [
    {
      "debugMessage": "Call to undefined method WC_Customer::set_shipping_email()",
      "message": "Internal server error",
      "category": "internal",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "updateCustomer"
      ]
    }
  ],
  "data": {
    "updateCustomer": null
  }
}

With phone input variable:

mutation UPDATE_CUSTOMER {
  updateCustomer(input: {shipping: {phone: "+19175551234", }, clientMutationId: "some-set-of-strings"}) {
    clientMutationId
  }
}

Response:

{
  "errors": [
    {
      "debugMessage": "Call to undefined method WC_Customer::set_shipping_phone()",
      "message": "Internal server error",
      "category": "internal",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "updateCustomer"
      ]
    }
  ],
  "data": {
    "updateCustomer": null
  }
}

Expected behavior

Shouldn't have the option to add shipping email or phone as input variables.

Screenshots

[kidunot89]

@ardiewen Yea, the CustomerAddressInput type used is by both the billing and shipping input fields.

It should be fine, if the mutation resolver just made to ignore the email and phone fields on the shipping field. 🤔