Dynamic or Untyped Mappings and Output

Thanks for what looks to be a great library! I’m creating an application that needs to do some CSV processing without knowing either the mappings or the structure of the input data at compile-time. At runtime I have both the input data (of course) and the mapping information (each of the destination columns and whether I should pull them from a column in the source or provide a default or static value).

So I have two questions:

1. Is there a way to construct the mapping object for TinyCsvParser at runtime? I guess I could construct a runtime expression manually using Linq. It would help if there were an overload to the mapping to pass in the column names as strings instead of just expressions (especially since it currently looks like the expressions are just mapped back to strings through reflection eventually).
2. Is there a way to receive some dynamic or IEnumerable<KeyValuePair<string, string>> (for header -> value) back from TinyCsvParser?

Thanks!

[bytefish]

Dynamic Mappings would be a great feature, but I am lacking the resources to implement it in the near future. Right now I prefer to have the library with fixed mappings. For sophisticated mappings people will turn to CsvHelpers anyway. This library is optimized for speed, so maybe this is what it should be known for.

I don’t want to generate false expectations, like users can expect me to support dynamic mappings sometime soon. So I am closing this issue.

Sorry! 🙏

[josh75337]

How do you recreate this warning? I downloaded the 2.1 branch and set it up and ran the unit test and did not get that warning.