Mapster
AutoMapper
Our great sponsors
Mapster | AutoMapper | |
---|---|---|
15 | 29 | |
4,110 | 9,719 | |
2.2% | 0.6% | |
5.5 | 8.1 | |
3 months ago | 6 days ago | |
C# | C# | |
MIT License | 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.
Mapster
-
Dotnet.World.News(Wednesday, September, 20, 2023)
🔴 [Mapster] A fast, fun and stimulating object to object Mapper! Mapster was designed to be efficient on both speed and memory. You could gain a 4x performance improvement whilst using only 1/3 of memory.
-
Object Mapping in .NET
Mapster
-
Is Automapper the most hated library?
Which is the main reason I don't use it anymore. I can still stand behind why it was created and what it was trying to solve. If you still want to use a mapper I would recommend Mapster as it supports source generation so you can see all code and it's references.
-
When using the DTO pattern and rolling your own mappers, is there a shorter way to write the mapping functions?
Gotta add a shoutout to Mapster which does pretty much the same thing also using source generation.
No sure if I understand your problem correctly, but maybe something like Mapster or Mapperly could help with that, given that it can generate source code instead of using reflection or expression trees.
-
AutoMapper's open source code of conduct
I highly recommend Mapster (https://github.com/MapsterMapper/Mapster)
-
What C# tools would you like to use that don't exist today?
We use Mapster coupled with FastExpressionCompiler and have been very happy with it.
-
Unit Tests Done Right (Part 2)
I hope I managed to convince you and proved the value of unit tests for mappings, so let's move on to the next example. We're going to use AutoMapper, but from a testing standpoint, the choice of mapper makes no difference. For instance, we can replace AutoMapper with Mapster and it won't affect our tests in any way. Moreover, the existing tests will indicate whether our mapping refactoring was successful or not, which is one of the points of having unit tests 🙂
- Comparison of Object Mapper Libraries
-
APIs de mapeamento valem à pena?
Writing mapping method is machine job. Do not waste your time, let Mapster do it. https://github.com/MapsterMapper/Mapster
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?
mapperly - A .NET source generator for generating object mappings. No runtime reflection.
GraphQL for .NET - GraphQL for .NET
Mapping Generator - :arrows_counterclockwise: "AutoMapper" like, Roslyn based, code fix provider that allows to generate mapping code in design time.
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.
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+.
ExpressMapper - Mapping .Net types
NancyFx - Lightweight, low-ceremony, framework for building HTTP based services on .Net and Mono. Note: This project is no longer maintained and has been archived.
MediatR - Simple, unambitious mediator implementation in .NET
ServiceStack - Thoughtfully architected, obscenely fast, thoroughly enjoyable web services for all