Fix #253, use user defined TypeHandlers over internal implementations. #258
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
basically SqlMapper was using its own internal IEnumerable type handling even if the user has defined their own type handler for IEnumerable types (e.g. List).
I've switched the order so it will check if the user has defined a type handler for this, and then use the IEnumerable implementation.
Also I added two tests, to DapperTests NET40 with a very simple List TypeHandler implementation that will read Strings into a List by splitting the string comma. And also will use join a list by comma and set a parameter from a List.