Skip to content

Missing commas in the Communication Services Email SDK samples for .NET C# #43143

Open
@Daniel-Krzyczkowski

Description

@Daniel-Krzyczkowski

Type of issue

Typo

Description

In the documentation about Azure Communication Services Email C# SDK (under this link) there are sample code snippets included.
However, there are missing commas in the code snippets.
Example:

try
{
    var emailSendOperation = emailClient.Send(
        wait: WaitUntil.Completed,
        senderAddress: "<Send email address>" <------------ missing comma // The email address of the domain registered with the Communication Services resource
        recipientAddress: "<recipient email address>" <------------ missing comma
        subject: "This is the subject",
        htmlContent: "<html><body>This is the html body</body></html>");
    Console.WriteLine($"Email Sent. Status = {emailSendOperation.Value.Status}");

    /// Get the OperationId so that it can be used for tracking the message for troubleshooting
    string operationId = emailSendOperation.Id;
    Console.WriteLine($"Email operation id = {operationId}");
}
catch ( RequestFailedException ex )
{
    /// OperationID is contained in the exception message and can be used for troubleshooting purposes
    Console.WriteLine($"Email send operation failed with error code: {ex.ErrorCode}, message: {ex.Message}");
}

In all snippets there should be proper commas included.

Page URL

https://learn.microsoft.com/en-us/dotnet/api/overview/azure/communication.email-readme?view=azure-dotnet

Content source URL

https://github.com/Azure/azure-docs-sdk-dotnet/blob/master/api/overview/azure/latest/communication.email-readme.md

Document Version Independent Id

24d20e7a-1fec-ec19-0ba7-55b0fe5608bc

Article author

@azure-sdk

Metadata

  • ID: 76c1c721-46fc-659e-b6b3-0c4100f26240
  • Service: communication

Metadata

Metadata

Assignees

No one assigned

    Labels

    ClientThis issue points to a problem in the data-plane of the library.CommunicationService AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions