Tomasz Maruszak

I don't think it will work as target netstandard2.0 and net6.0, there's a call out: > As this solution is based on interceptors, only .NET 8+ is supported

.NET Standard is still needed to enable this library for the .NET Framework. So I will want to keep it around. If you look at other libraries they also target...

There isn't anything like that. Please provide an example how you'd configure it inside the AddSlimMessageBus(). It could be added, I just wonder if that's a common need across most...

For memory bus, there is a nice feature to [auto declare](https://github.com/zarusz/SlimMessageBus/blob/master/docs/provider_memory.md#auto-declaration) the producers/consumers and line them up in the respective topics. That prevents users from having to do declarations (including...

Are you planning a PR improve this? If this something that is a priority for your project?

When the interceptors where introduced they were running intentionally on the same scope as the message handling scope (I wanted the interceptors to have access to the ongoing/current message scope)....

@EtherZa could you update the spike link provided? Its currently broken. I like the middleware approach 5), as an option the middleware could decide if to redo the scope (default...

Given the scope re-create feature is handled as part of #354, I suggest we leave the pipeline revamp exploration to another bigger milestone 4.0.0, once the 3.0.0 is released.

So yes, the kafka provider moves forward which is not desired in your case. This is a standardized way to tap into error handling (in case you haven't seen it):...

> How can I generate manual commit on the "SlimMessageBus.Host.Kafka" library? Since the "EnableAutoCommit" property is set to "false" in the "CreateConsumer" method of the "KafkaGroupConsumer" class. The current version...