Chau Tran

What about making `AutoMap` accepts additional information like: ```ts // 👇 this needs better naming @AutoMap({ type: () => [String], flattenSourcePath: ['foos', 'id']}) fooIds: string[] // it doesn't matter how...

1. I agree dot notation looks cleaner. However, the internal of AutoMapper works with an array of paths instead so it's easier for AutoMapper to work with array. 2. Can...

Yeah, the "refactor-able" makes sense to me. I'll think about it. This won't work for applications that use "mangle" when obfuscating/minimizing code for production. We might be able to make...

Thanks @LennartH for the offer!! You can start here: https://github.com/nartc/mapper/blob/main/packages/core/src/lib/mapping-configurations/for-member.ts#L31 to see how a `Selector` is turned into a `string[]`. Although, I would still think `Selector` with Array seems weird...

@LennartH I'm using npm v6 still. I'd love to change to `pnpm` but I need `patch-package` at the moment :(

This is harder that I thought it would. A lot more involved than anticipated. I have some time now after a month busy and dealing with personal stuffs. Will look...

@micalevisk just FYI, I've spent a couple of hours trying to pull something together but still haven't been able to come up with a clean solution for this so it...

Absolutely yes!

@Jordan-Hall I'd rather do separate but if you have no problem with a build process of an extension for this type of thing then I'm fine either way

@rosostolato have you looked at this article? https://itnext.io/how-to-enjoy-signal-based-input-right-now-56efecaeee98