Mapster
QueryR
| Mapster | QueryR | |
|---|---|---|
| 15 | 6 | |
| 4,145 | 32 | |
| 0.8% | - | |
| 5.5 | 10.0 | |
| 5 months ago | over 1 year 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.
- Mapster and IFormFile exception
-
Object Mapping in .NET
Mapster
-
Help with an ASP.NET Core API and Mapster
Have you read this part in their documentation? https://github.com/MapsterMapper/Mapster/wiki/Data-types
-
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.
-
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.
-
Looking for alternative solution to Deep Clone for 10,000+ iterrations
Try Mapster
-
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 🙂
QueryR
-
I made a new filtering library for .NET projects
I love it. I did something similar with my QueryR project.
- What C# tools would you like to use that don't exist today?
- Is there an equivalent of Hypothesis (python) for xunit
-
API filtering, pagination and sorting
I of course also take it a step further and feed the parameters to my expression tree generating library QueryR or QueryR.EntityFrameworkCore.
- REST API using dotnet.
-
Introducing QueryR!
QueryR - https://github.com/craigmccauley/QueryR
What are some alternatives?
AutoMapper - A convention-based object-object mapper in .NET.
Superpower - A C# parser construction toolkit with high-quality error reporting
mapperly - A .NET source generator for generating object mappings. No runtime reflection.
dnSpy - Unofficial revival of the well known .NET debugger and assembly editor, dnSpy
Mapping Generator - :arrows_counterclockwise: "AutoMapper" like, Roslyn based, code fix provider that allows to generate mapping code in design time.
Msharp - M# is a pioneering project that showcases the full range of features and functionalities that a REST web API should possess.
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+.
Ooze - This package provides simple mechanism for applying filters, sorters, paging to your IQueryable<T> queries.
ExpressMapper - Mapping .Net types
System.Linq.Dynamic.Core - The .NET Standard / .NET Core version from the System Linq Dynamic functionality.
mapr - A simple object to object mapper.
Ooze.Query - This package enables usage of Readable Queries on IQueryable<T> instances. This is a concept where you can write actual expression as a string representation for filtering.