MediatR
AutoMapper
Our great sponsors
MediatR | AutoMapper | |
---|---|---|
53 | 29 | |
10,533 | 9,719 | |
- | 0.6% | |
6.2 | 8.1 | |
2 days ago | 7 days ago | |
C# | C# | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MediatR
-
The Monad Invasion - Part 2: Monads in Action!
You probably noticed that .SetName() returns a Either. You may have come across Unit in libraries like MediatR or Language-Ext. It's a simple construct representing a type with only one possible value. We use it as a placeholder for operations that do not return a value but may return another state. In our example, .SetName() is a Command that does not return a value but may fail. Therefore, the monad Either carries two possible states: Right (without value) or Left (with an Error).
-
How small is the smallest .NET Hello World binary?
The widely used MediatR library[0] could be used to do that as well, just FYI.
- Exception handling between controller and service
-
Is MediatR the only real CQRS solution for .Net?
From: https://github.com/jbogard/MediatR
-
Easiest way to build the fastest REST API in C# and .NET 7 using CQRS
I gave it a go and I was impressed how easy and fast it was to set it all up. Since I'm not a big fan of REPR pattern almost all my projects are using CQRS pattern with a help of MediatR ](https://github.com/jbogard/MediatR) I immediately started going over something similar that Fast Endpoints offer which is a command bus.
-
MVVM Question: How do you manage the interaction between Model and ViewModel?
I'd use a dedicated event bus based on Reactive Extensions or MediatR to publish domain events from your domain services. This probably doesn't solve all your ViewModel update problems as is, maybe you need to revise the granularity (maybe you can have smaller ViewModels that refresh single property that exposes the Model) and lifespan (sometimes you can create a ViewModel, make it perform it's task and then discard it completely) of your ViewModels.
Typically if you want to notify interested parties (ViewModels in case of WPF) of Model changes you'd use some kind of pub-sub mechanism like Reactive Extensions or MediatR. Your ViewModel can subscribe to an event bus of some kind (either standalone or maybe exposed by an Aggregate if you follow DDD), your domain logic (which should be located in Model layer, not in ViewModel layer: Service, Repository, DDD Aggregate or whatever you'd like to call it) will then do something useful with your Model and publish the corresponding event to the event bus.
-
Async Methods after setting a property.
If you're finding yourself in a situation where you need to turn this behavior into a pattern because there are a lot of View Models that need to execute async business logic in response to some changes, I'd go with something like MediatR or Reactive Extensions. The idea is, again, that some other, probably business-level, component listens to changes in a decoupled way (that means it doesn't subscribe directly to your View Model, but to an event bus instead). View Model publishes change events to the event bus, and business-component reacts to these events by executing the business logic.
-
I don't get why I should use Redux
What people really want is to design the logic of an app independently from the component hierarchy. That means you need to store state somewhere other than the components and you need to dispatch events that are not attached to the component hierarchy. Also, a one way data flow has well known benefits as described by things like CQRS, RabbitMQ, and MediatR.
-
Nightclub Website
MediatR - for CQRS
AutoMapper
-
Object Mapping in .NET
AutoMapper
- New Google Bard Update (can run code)
-
AutoMapper's open source code of conduct
The only interesting one I found was https://github.com/AutoMapper/AutoMapper/issues/4226 and again, that wasn't automapper's issue, but just how expression engine in C# works. And author resolved it by himself.
While AutoMapper's use has its pros and cons this post is about their code of conduct on their GitHub repository, consider it a rant, or not.
-
Nightclub Website
AutoMapper - well for automapping
-
How to avoid AutoMapper configuration runtime errors
When working with AutoMapper, we often bump into runtime errors due to invalid mapping configuration, such as this one:
-
How to Build a WEB API ASP.NET Core 6
What problems will resolve automapper?
-
We released a new version of ShapeShift (0.4.0) - A lightweight Kotlin first library for Object Mapping. Would love to hear your thoughts!
I'm wondering myself. Most mappers like https://automapper.org/ will make a best effort mapper automatically via introspection. If this is just a DSL/annotation suite that requires explicit, complete mapping implementations then this strikes me as a re-implementation of parts of kotlin in kotlin.
-
Could someone point me towards a resorce to better understand how Automapper is supposed to be set up and configured?
If you wan't to know some internals, just read the source code, automapper is opensourced.
What are some alternatives?
Mapster - A fast, fun and stimulating object to object Mapper
mapperly - A .NET source generator for generating object mappings. No runtime reflection.
Mediator.Net - A simple mediator for .Net for sending command, publishing event and request response with pipelines supported
GraphQL for .NET - GraphQL for .NET
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Polly - Polly is a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner. From version 6.0.1, Polly targets .NET Standard 1.1 and 2.0+.
Mapping Generator - :arrows_counterclockwise: "AutoMapper" like, Roslyn based, code fix provider that allows to generate mapping code in design time.
Brighter - A framework for building messaging apps with .NET and C#.
Hot Chocolate - Welcome to the home of the Hot Chocolate GraphQL server for .NET, the Strawberry Shake GraphQL client for .NET and Banana Cake Pop the awesome Monaco based GraphQL IDE.
ExpressMapper - Mapping .Net types
AgileMapper - A zero-configuration, highly-configurable, unopinionated object mapper with viewable execution plans. Flattens, unflattens, deep clones, merges, updates and projects queries. .NET 3.5+ and .NET Standard 1.0+.
ApiEndpoints - A project for supporting API Endpoints in ASP.NET Core web applications.