Skip to content

Commit

Permalink
Update generated code (#1588)
Browse files Browse the repository at this point in the history
update generated code
  • Loading branch information
async-aws-bot authored Oct 17, 2023
1 parent 6b396ad commit 02fa7fe
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 2 deletions.
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@
### Changed

- Allow passing explicit null values for optional fields of input objects
- AWS enhancement: Documentation updates.

## 1.6.0

Expand Down
4 changes: 3 additions & 1 deletion src/ValueObject/EmailContent.php
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,9 @@ final class EmailContent
* - All of the required header fields must be present in the message.
* - Each part of a multipart MIME message must be formatted properly.
* - If you include attachments, they must be in a file format that the Amazon SES API v2 supports.
* - The entire message must be Base64 encoded.
* - The raw data of the message needs to base64-encoded if you are accessing Amazon SES directly through the HTTPS
* interface. If you are accessing Amazon SES using an Amazon Web Services SDK, the SDK takes care of the base
* 64-encoding for you.
* - If any of the MIME parts in your message contain content that is outside of the 7-bit ASCII character range, you
* should encode that content to ensure that recipients' email clients render the message properly.
* - The length of any single line of text in the message can't exceed 1,000 characters. This restriction is defined in
Expand Down
4 changes: 3 additions & 1 deletion src/ValueObject/RawMessage.php
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,9 @@ final class RawMessage
* - All of the required header fields must be present in the message.
* - Each part of a multipart MIME message must be formatted properly.
* - Attachments must be in a file format that the Amazon SES supports.
* - The entire message must be Base64 encoded.
* - The raw data of the message needs to base64-encoded if you are accessing Amazon SES directly through the HTTPS
* interface. If you are accessing Amazon SES using an Amazon Web Services SDK, the SDK takes care of the base
* 64-encoding for you.
* - If any of the MIME parts in your message contain content that is outside of the 7-bit ASCII character range, you
* should encode that content to ensure that recipients' email clients render the message properly.
* - The length of any single line of text in the message can't exceed 1,000 characters. This restriction is defined in
Expand Down

0 comments on commit 02fa7fe

Please sign in to comment.