Do you have an API in mind, so I can get an idea? Then we could see, what’s possible and eventually make a new major release and changes to the existing API. 🙂

The only requirement for an API is that the mapping class (it must be custom) would have to call the constructor explicitly. If you use reflection, there is a complicated way to do that, but I think the simplest API would be one that allows the mapping class to extract the column values, then call the constructor, and return the instance to your infrastructure. You already have a way to extract column values (strong typing there would be bonus).

Currently the CsvMapping class requires a parameter less constructor.

You could make an equivalent to CsvMapping specifically for immutable types.

If you want to simply extend the MapUsing API, you could have a delegate parameter that does not take the instantiated object as input, only the values. Then a null return value means failure, or if you allow value types to be constructed, a Result structure is returned, and your base class (CsvImmutableMapping) would need to have a MapUsing method that accepts the correct delegate type (i.e., the delegate is strongly typed by its output).

Sounds good! I think using records also makes a lot of sense and updating the API for it. But I cannot really promise, when I’ll be able to look at it. Any help is appreciated. 👍

I had a try at this, and I believe both MapUsing and a similar syntax to the existing MapProperty methods can be interesting.
Feel free to have a look at PR #85 and see if it fulfills your needs.

A great PR! Please give me some time to take a look at it. :)