IMappingServices bug - Map does not detect collection types before TypeMap assertion #126
Comments
ghost
assigned
jbatte47
added a commit
to jbatte47/code-patterns
that referenced
this issue
Nov 20, 2013
- Updated MappingServices to use underlying types for collections - Created MappingServices feature to verify functionality
jbatte47
added a commit
to jbatte47/code-patterns
that referenced
this issue
Nov 20, 2013
- Updated MappingServices to use underlying types for collections - Created MappingServices feature to verify functionality
jbatte47
added a commit
to jbatte47/code-patterns
that referenced
this issue
Nov 20, 2013
- Updated MappingServices to use underlying types for collections - Created MappingServices feature to verify functionality
jbatte47
added a commit
that referenced
this issue
Nov 20, 2013
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Source and destination types should be inspected before checking for an existing
TypeMap. If both are enumerable types, the underlying element types should be resolved, otherwise, the original source and destination types should be valid for direct use.The text was updated successfully, but these errors were encountered: