Make addresses[].id JSON property deprecated, remove it, or fix UI bug

The following is a snippet from the user JSON schema. I found that if you include an id value for a user address, when you edit the user using the FOLIO web application and try to save the user, the combo box for address type is cleared and you receive a validation error. I've noticed that it only does this if there is an id value for the address. If it's not there, it works fine. I'm guessing maybe the UI code is referencing the field positionally or something.

        },
        "addresses": {
          "description": "Physical addresses associated with the user",
          "type": "array",
          "items": {
            "type": "object",
            "additionalProperties": false,
            "properties": {
              "id": {
                "description": "A unique id for this address",
                "type": "string"
              },
              "countryId": {
                "description": "The country code for this address",
                "type": "string"
              },

I think the id field isn't actually used. If this is the case, can you mark it as deprecated, or remove it? Otherwise, can you fix the FOLIO web application so that the address type combo box doesn't malfunction if the id value is present?

I've noticed elsewhere in the JSON schemas, where a value of "Deprecated" is set in the description property for deprecated values.

    "createdDate": {
      "description": "Deprecated",
      "type": "string",
      "format": "date-time"
    },