Jeremy D. MillerJust urging folks to not just try to shoehorn Wolverine in as a drop in replacement for MediatR:
Wolverine Idioms for MediatR Users https://jeremydmiller.com/2026/01/26/wolverine-idioms-for-mediatr-users/
Khalid ⚡@jeremydmiller From this post, how is Cart resolved in AddToCartRequestEndpoint? Is it coming from the IoC and expected to resolve?
I would guess there's something else that pulls user information to get "their cart” that isn't shown here.
Update: reading the docs is helpful :) https://wolverinefx.net/guide/handlers/persistence.html#automatically-loading-entities-to-method-parameters
Beat Walti@khalidabuhakmeh @jeremydmiller as far as I've understood Wolverine and Marten, the request probably must have a cartId which is then used to load the appropriate Cart event stream to which the addProductRequest gets appended to.
If I recall correctly, Wolverine generates corresponding "boilerplate" code around during compile time and nowadays leverages IoC to fetch services. The "Cart" is however an Aggregate most probably, thus it will use Marten to fetch the corresponding stream..
If I recall correctly, Wolverine generates corresponding "boilerplate" code around during compile time and nowadays leverages IoC to fetch services. The "Cart" is however an Aggregate most probably, thus it will use Marten to fetch the corresponding stream..
@bibolorean @jeremydmiller Yep, that's correct. Found that after reading the documentation. :). I should have read the docs, but luckily, no one had to tap the sign. 😅
@bibolorean @khalidabuhakmeh If you were using Marten, sure. You'd have our flavor of the "Decider Pattern". The [Entity] thing in that blog post works for EF Core too though. Just no event sourcing for EF Core (yet)