You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In theory, programmatically mapping a subscription route should work like the following:
// Map the route for both HTTP and Daprapp.MapPost("/messages",handler).WithTopic("redis-pubsub","employeemessage",true)// This enables Dapr subscription - true == raw messages.WithName("ProcessMessage").WithTags("Messages").WithOpenApi();
Actual Behavior
However in this case, the subscriber is not able to parse the message as it is expecting an octet-stream.
Expected Behavior
In theory, programmatically mapping a subscription route should work like the following:
Actual Behavior
However in this case, the subscriber is not able to parse the message as it is expecting an octet-stream.
The code above returns:
Steps to Reproduce the Problem
Follow the instructions here: https://github.com/rochabr/mediatr-dapr-sample and make the necessary changes within
MessageModule.cs
andProgram.cs
In theSubscriber.API
project.To bypass the issue, I had to map the subscription endpoint explicitly:
The text was updated successfully, but these errors were encountered: