Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating Java SDK to include inline attachments #41591

Conversation

natekimball-msft
Copy link
Member

Description

This update introduces the new EmailAttachment property contentId, the presence of which will be used to mark an attachment for inline rendering. The contentId property should be referenced in the HTML body of the email attachment.

Link to swagger spec API: Azure/azure-rest-api-specs#29699

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@azure-sdk
Copy link
Collaborator

API change check

APIView has identified API level changes in this PR and created following API reviews.

com.azure:azure-communication-email

Copy link
Member

@kagbakpem kagbakpem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awaiting feature implementation of partner team prior to merge to main.

Copy link
Member

@DominikMe DominikMe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm with small suggestion

@kagbakpem kagbakpem merged commit c81ab5e into Azure:main Sep 20, 2024
19 checks passed
natekimball-msft added a commit to Azure/azure-sdk-for-js that referenced this pull request Sep 20, 2024
### Packages impacted by this PR

azure/communication-email

### Issues associated with this PR

N/A

### Describe the problem that is addressed by this PR

N/A

### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?

N/A - update to include contentId property for EmailAttachment to
support inline attachments.

### Are there test cases added in this PR? _(If not, why?)_

Yes

### Provide a list of related PRs _(if any)_

[Java SDK PR](Azure/azure-sdk-for-java#41591)
[.NET SDK PR](Azure/azure-sdk-for-net#45360)
[REST API PR
(complete)](Azure/azure-rest-api-specs#29699)

### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_

Git command?
git push --set-upstream origin
natekimball/update-js-sdk-for-inline-attachments

### Checklists
- [X] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [X] Added a changelog (if necessary)
mssfang pushed a commit to mssfang/azure-sdk-for-java that referenced this pull request Oct 21, 2024
* updating Java SDK to include inline attachments

* minor updates

* updating classes with correct API version

* updating tests

* assets.json

* reverting version number

* content should be string

* actually it should be BinaryData, my bad

* merge miss

* fixing linting errors and sample

* linting error

* another linting error

* adding older methods to bypass linting errors

* reordering enum for linting error in pipeline

* cleaning up trailing whitespace

* appending setContentId to end of constructor call
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants