Stripe CLI sends metadata fields that contain a dot as arrays

[jtorreguitarcompass]

Issue

I was trying to trigger an event through the CLI using the following command:

stripe trigger payment_intent.payment_failed --add payment_intent:metadata."Order No."="37018189"

Which returned the following response:

Trigger failed: Request failed, status=400, body={
  "error": {
    "message": "Invalid value type: [\"37018189\"] must be a string",
    "param": "metadata",
    "request_log_url": "https://dashboard.stripe.com/test/logs/req_QcLulON5e8gLUe?t=1682686037",
    "type": "invalid_request_error"
  }
}

When visiting the URL provided the request shows the value for that metadata field was sent as an array:

{
  "description": "(created by Stripe CLI)",
  "metadata": {
    "Order No": [
      "37018189"
    ]
  },
  "currency": "usd",
  "payment_method": "pm_card_chargeDeclined",
  "confirm": "true",
  "amount": "2000",
  "payment_method_types": [
    "card"
  ]
}

When I remove the dot at the end of the "Order No." metadata field the request is sent as desired (with the value as a string instead of an array). The successful command would be:

stripe trigger payment_intent.payment_failed --add payment_intent:metadata."Order No"="37018189"

Expected Behavior

I expected the "Order No." value to be sent as a string. Something like so:

{
  "description": "(created by Stripe CLI)",
  "metadata": {
    "Order No.": "37018189"
  },
  "currency": "usd",
  "payment_method": "pm_card_chargeDeclined",
  "confirm": "true",
  "amount": "2000",
  "payment_method_types": [
    "card"
  ]
}

Steps to reproduce

Trigger a stripe event with the param containing a dot like in the first command shown:

stripe trigger payment_intent.payment_failed --add payment_intent:metadata."Order No."="37018189"

Traceback

https://dashboard.stripe.com/test/logs/req_QcLulON5e8gLUe?t=1682686037

Environment

macOS