The example of SendRawEmailCommand does not match the docs so the example fails if you try to replicate

[LucasGarci]

Describe the issue

The example shows no base64 encoding

// The following example sends an email with an attachment:
const input = {
  "Destinations": [],
  "FromArn": "",
  "RawMessage": {
    "Data": "From: [email protected]\\nTo: [email protected]\\nSubject: Test email (contains an attachment)\\nMIME-Version: 1.0\\nContent-type: Multipart/Mixed; boundary=\"NextPart\"\\n\\n--NextPart\\nContent-Type: text/plain\\n\\nThis is the message body.\\n\\n--NextPart\\nContent-Type: text/plain;\\nContent-Disposition: attachment; filename=\"attachment.txt\"\\n\\nThis is the text in the attachment.\\n\\n--NextPart--"
  },
  "ReturnPathArn": "",
  "Source": "",
  "SourceArn": ""
};
const command = new SendRawEmailCommand(input);
const response = await client.send(command);
/* response ==
{
  "MessageId": "EXAMPLEf3f73d99b-c63fb06f-d263-41f8-a0fb-d0dc67d56c07-000000"
}
*\/
// example id: sendrawemail-1469118548649

But the docs especifies that it need to be base64 encoded

Links

https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/preview/client/ses/command/SendRawEmailCommand/

[kuhe]

RawMessage.Data is declared as a blob type, and the current JSv3 implementation is to require a Uint8Array for blob type inputs that are not modified (i.e. type-widened) by the streaming trait, which does not apply in this case.

Using the example as-is may cause a type error when a string instead of a Uint8Array is provided. As part of ongoing work to simplify type conversions for Blobs in #4265, we will try to cover the case where a Uint8Array blob representation is currently required but the user supplies a string. We will aim to add automatic conversion in these cases.

[kuhe]

The docs mention base64 encoding, but this is something that the AWS SDKs do for you, if you provide the expected Uint8Array.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.