Tim M

Mb 😅, knew this had a load of related issues and saw "circular reference" in the title. I'll fix it

> Is there sth. which hinders us to implement this for all kind of mappings instead of just IQueryable projections? Don't think so, just didn't see a massive need to....

> @TimothyMakkison what is the status on this one? Should I review again? Super sorry for abandoned this. Iirc this PR was nearish to completion - Haven't added documentation -...

Thanks for this, i briefly look into it. Are switch expressions supported for `IQueryable`? ### Also should the source parameter be `IQueryable`, can't look at the tests or source code...

> @TimothyMakkison The switch expression doesn't happen inside the `Expression`/`Select`, therefore I think it should work. Thanks, I was a little confused because the docs only mentioned the object source...

Sorry, I was suggesting that an issue needs to track each variant of generic mapping for IQueryable and for generic existing target mapping

Would #513 and #201 help?

Good point with 513. If #201 supports adding ignores then it will be perfect for you. Failing that it would be pretty easy to modify the `IgnoreObsolete` code to support...

Hey, unfortunately Mapperly doesn't support automatic unflattening yet. Instead you can try using [`[MapProperty]`](https://mapperly.riok.app/docs/configuration/flattening) ```C# [Mapper] public static partial class Mapper { [MapProperty("FooBar", "Foo.Bar")] public static partial Destination Map(Source src);...

Would it be worth adding regex support here? This way we don't have to add suffix and custom ignores as well. ```C# [MapperIgnore("Local\w*")] // ignores all members starting with "Local"...