Rafael Kallis

for those interested, I have implemented a solution for this from scratch in a project of mine (closed source for the public, willing give access to @kamilmysliwiec if he wants...

@xdave I am considering creating a library that exposes an abstract mediator (command bus) class, so that clients can create reusable concrete mediators. I am sure there are codebases beyond...

Event handlers shouldn't be a problem either, they are also part of mediatR actually, under the name "notifications" (https://github.com/jbogard/MediatR/wiki#notifications). I also assume sagas are easy to manage since they also...

@xdave the answer is very simple: the mediator is request-scoped, therefore any mediator client becomes request-scoped :) so I can imagine sagas will also become request-scoped.

> This prevents the Mediator from running continuously in the background to listen for incoming events that may be triggered by outside forces, timers, or from code that is being...

some more thoughts: > custom scopes A low level api for custom scopes exists actually. `ContextIdFactory.create()` is the fundamental building block for custom scopes, one only has to provide an...

No, ExecutionContext is not an abstraction over moduleRef. Let me illustrate with an example: ```ts // scope abstraction, can originate from requests, timers, cron, amqp consumers, etc. @Injectable() class Scope...

after some reading I got it to work by changing `qdbus` to `qdbus-qt5`

I am facing the exact same problem, only difference compared to @Rudomitori 's example is that we have a `text[]` column instead of `integer[]`. We have a historic migration (from...

Also stuck here. I have no extension point to make it work. Openapi spec:  Generated enum:  Generated class that uses the enum:  The serialized enum value is...