Jan Trejbal
Jan Trejbal
I will squash it to the required commit message after the review
No worries, I understand it as a one-at-the-time. I was ok to wait until the static PR made it :)
Hello @TimothyMakkison I run a small benchmark: ```cs using BenchmarkDotNet.Attributes; using BenchmarkDotNet.Jobs; namespace Sandbox; public record A(int Value); public record D(int Value); public record struct As(int Value); public record struct...
I have run this benchmark 3times (first without struct and memory info) and the numbers were always in this way. I did not dig into the reason why NET8 is...
Sure: DTOs: ```cs class A { public B Value { get; set; } } class B { public int Value { get; set; } } class C { public D...
> Also the hydration seems to be kind of EF Core related That's possible, I have no experience with different engines using IQueryable. > An alternative implementation could be based...
I understand the meaning of `IgnoreMappingMethodAttribute`. The issue: Right now, in Mapperly there is an artificial condition that prevents using `ByName` enum mappings instead of calling the mapping method `MapToE2`....
I want only a necessary part to be executed on the client. 😃 Database entity: ```cs class Entity { public int Id { get;set; } public MyEnum Type { get;set;...
Yes, I think that it's good and safer. You can have a custom getter in a property, and with the current solution, it's executed twice.
The `UnsafeAccessorAttribute` is not really related to the issue. I just spot it there when looking for a new features :) (thank you for these btw)