Skip to content

Conversation

stijnmoreels
Copy link
Member

Use a more dev-friendly approach that removes the Azure... prefix noise from the handlers and message context, and places them in the Arcus.Messaging namespace.

@stijnmoreels stijnmoreels added enhancement New feature or request area:message-processing All issues related to how we process the messages labels Aug 1, 2025
Copy link

netlify bot commented Aug 1, 2025

Deploy Preview for arcus-messaging canceled.

Name Link
🔨 Latest commit 9005f69
🔍 Latest deploy log https://app.netlify.com/projects/arcus-messaging/deploys/68b181a3163b9200083e4392

/// <param name="entityType">The type of Azure Service bus entity that the <paramref name="eventArgs"/> receives from.</param>
/// <param name="eventArgs">The Azure Service bus event arguments upon receiving the message.</param>
/// <exception cref="ArgumentNullException">Thrown when one of the parameters is <c>null</c>.</exception>
public static AzureServiceBusMessageContext Create(
Copy link
Member Author

Choose a reason for hiding this comment

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

note: we haven't released the session-aware pump yet, so we can safely move it again here.

@stijnmoreels
Copy link
Member Author

Maybe the more responsible approach would be to move this enhancement to v4.0, as there are already a lot of changes happening on v3.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:message-processing All issues related to how we process the messages enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant