`metadata.nullable` is inconsistent (E.g. customer vs subscription)

[broccolihighkicks]

Both the Customer and Subscription schema have a metadata property:

  "metadata": {
      "additionalProperties": {
          "maxLength": 500,
          "type": "string"
      },
      "description": "...",
      "type": "object"
  },

But the Subscription lists metadata in the required fields list:

        "required": [

            "metadata",
        ],

Does this imply that the metadata field is nullable for the customer object, but not for the subscription object?

Why is metadata required on the subscription but not the customer?

The docs both show this for both objects (no required tag):

[remi-stripe]

@broccolihighkicks It's mostly an inconsistency on our end whether we return metadata: null, metadata: {} or no metadata key at all in the response. It shouldn't have much impact beyond that but it's something we'd like to fix in the future so I'm going to tag this as future!