spectre.console VS Mapster

I like this one for .NET https://github.com/spectreconsole/spectre.console which I found in this list https://github.com/shadawck/awesome-cli-frameworks.

The following code sample (a console project) uses Spectre.Console NuGet package to provide easy methods for gathering user input like first and last name of type string or perhaps birth date for a DateOnly property.

🔴 [spectre.console] A .NET library that makes it easier to create beautiful, cross platform, console applications.

https://github.com/spectreconsole/spectre.console for doing pretty Cli applications

A friend and me have been working on an opinionated wrapper around the popular Spectre.Console. We call it SpectreCoff (Spectre.Console for F#).

Spectre.Console for enhanced console writting.

Add the NuGet package Spectre.Console to the project

By using open source library like Spectre.Console creating useful console applications easy. Spectre.Console also makes it easy to create dotnet tools, see documentation and check out their GitHub repository.

🔴 [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

Have you read this part in their documentation? https://github.com/MapsterMapper/Mapster/wiki/Data-types

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.

Gotta add a shoutout to Mapster which does pretty much the same thing also using source generation.

I highly recommend Mapster (https://github.com/MapsterMapper/Mapster)

We use Mapster coupled with FastExpressionCompiler and have been very happy with it.

Try Mapster

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 🙂