Skip to content

chore(general): remove deprecated general 'route message' with string #576

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

stijnmoreels
Copy link
Member

👉 Since we're working on v3.0, we can start removing stuff for real.

This PR removes the deprecated IMessageRouter.RouteMessageAsync method that takes in a string message in favor of concrete type implementations in message pump/router solutions.

@stijnmoreels stijnmoreels requested a review from fgheysels as a code owner May 27, 2025 08:33
@stijnmoreels stijnmoreels added the area:message-processing All issues related to how we process the messages label May 27, 2025
Copy link

netlify bot commented May 27, 2025

Deploy Preview for arcus-messaging ready!

Name Link
🔨 Latest commit d7fc075
🔍 Latest deploy log https://app.netlify.com/projects/arcus-messaging/deploys/683578dbbb29680008a1c6e1
😎 Deploy Preview https://deploy-preview-576--arcus-messaging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@@ -10,24 +8,5 @@ namespace Arcus.Messaging.Abstractions.MessageHandling
[Obsolete("Will be removed in v3.0 as only concrete implementations of message routing will be supported from now on")]
public interface IMessageRouter
Copy link
Member

Choose a reason for hiding this comment

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

Why don't we remove the interface entirely ?

Copy link
Member Author

Choose a reason for hiding this comment

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

Step by step, keeping changes separated to reduce ripple effects.

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants