Jim Welch comments

Results 6 comments of


                                            Jim Welch

option to throw when result set has unmapped columns

This gets my upvote, even a debug only option would be helpful. With larger projects and teams this is a constant issue with Dapper.

option to throw when result set has unmapped columns

Pollute? That is a specious argument. Making software work by surfacing errors because of "sloppiness" isn't a bad idea, it helps make frameworks usable.

option to throw when result set has unmapped columns

Using EF. Dapper is "a simple object mapper", not an ORM. It is the object mapping feature that would be easier to use and support if failures are not always...

option to throw when result set has unmapped columns

Now your being just silly @DarekDan, keep it professional. An object mapper that fails to map throwing an exception doesn't come anywhere close to a SRP violation. Thanks for the...

option to throw when result set has unmapped columns

Dapper is not an object mapper? Why is it then that the title in the Readme is "Dapper - a simple object mapper for .Net"?

option to throw when result set has unmapped columns

In my view, failing as close to the error as possible improves your ability to test. If a mapping fails because of a change to a query the unit test...