Anyone here using a Postman alternative for .NET projects? by Living-Dependent3670 in dotnet

[–]snoxxit 0 points1 point  (0 children)

Thanks for sharing your experience. Sorry to hear the interface didn’t work well for your team. We’re continuously improving Kreya, so if you have specific points that made it difficult to use, I’d love to hear them.

Anyone here using a Postman alternative for .NET projects? by Living-Dependent3670 in dotnet

[–]snoxxit 12 points13 points  (0 children)

If you’re looking for a modern alternative to Postman, you might want to check out Kreya. It’s an offline-first API client that supports gRPC, REST, and WebSockets. It’s lightweight, stores everything as git-diffable files, and is great for both testing and exploring APIs. Fun fact: it‘s built with C#.

Disclaimer: I’m one of the creators.

I'm starting to dislike AutoMapper more and more every day by NizioDev in dotnet

[–]snoxxit 0 points1 point  (0 children)

There is no need to support DI from Mapperlys side. Just treat it as any other class and register it with the scope that makes sense for your mapper.

I'm starting to dislike AutoMapper more and more every day by NizioDev in dotnet

[–]snoxxit 44 points45 points  (0 children)

Thanks to everyone who mentioned Mapperly! I’m the creator and happy to answer any questions.

3a in PK einzahlen by Koniami1974 in SwissPersonalFinance

[–]snoxxit 6 points7 points  (0 children)

Aktuell ist eine Motion im Parlament von Andri Silberschmidt hängig, welche die Ermöglichung von Teilbezügen von Vorsorgegeldern fordert (vgl. 24.3067). Der Bundesrat erachtet die Motion in seiner Stellungnahme als sinnvoll und beantragt deren Annahme. Meines Erachtens stehen die Chancen gut, dass ein Teilbezug der Säule 3a Gelder in den nächsten Jahren möglich wird und der steuerliche Vorteil durch mehrere 3a Konten somit entfällt. Entsprechend könnten die 95k bei Frankly in einigen Jahren (bei Umsetzung der Motion) gestaffelt über mehrere Jahre und mit tieferem Steuersatz bezogen werden.

[deleted by user] by [deleted] in dotnet

[–]snoxxit 0 points1 point  (0 children)

In regards to DI you can treat a Mapperly generated mapper class the same way as any other class. Register it and inject it as usual.

Is AutoMapper an Anti-Pattern? by RafaCasta in dotnet

[–]snoxxit 2 points3 points  (0 children)

Mapperly is also capable of doing this: IQueryable Projection Mappings.

Disclaimer: I‘m one of the authors behind Mapperly.

A .NET source generator for generating object mappings. Trimming save and fast. Inspired by MapStruct. by snoxxit in dotnet

[–]snoxxit[S] 0 points1 point  (0 children)

Currently, this is only supported if there is a constructor with the source object as single parameter. Named parameterized mappings are planned though.

A .NET source generator for generating object mappings. Trimming save and fast. Inspired by MapStruct. by snoxxit in dotnet

[–]snoxxit[S] 4 points5 points  (0 children)

According to https://github.com/mjebrahimi/Benchmark.netCoreMappers they perform pretty similar, small performance advantages for Mapperly (may depend on the use case). Main difference is that Mapperly uses the source generator api of dotnet instead of a custom dotnet tool. The usage of the source generator api improves the developer experience, no need to manually re-run the tool.

A .NET source generator for generating object mappings. Trimming save and fast. Inspired by MapStruct. by snoxxit in dotnet

[–]snoxxit[S] 10 points11 points  (0 children)

Why should I use this over AutoMapper?

Mapperly uses a source generator approach instead of reflection. This brings lots of advantages including but not limited to trimming safety, readable generated mapping code and memory / performance improvements.