Replies: 2 comments 7 replies
-
I don't know. It seems easier to debug things when the error is thrown where the problem is. What's the point of throwing later, how is that better? You'd have to go back and find the mapping in question. |
Beta Was this translation helpful? Give feedback.
7 replies
-
This discussion has been automatically locked since there has not been any recent activity after it was closed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Mapping configuration
Version: 12.0.1
Expected behavior
Maps are created and when calling
mapperConfiguration.AssertConfigurationIsValid();
an error is thrown. (Same as when adding duplicate mappings of non open generics)Actual behavior
Maps are not created and a duplicate key exception is thrown.
Steps to reproduce
Run the
GenericsTests
changing theCreate Configuration
as per above snippetBeta Was this translation helpful? Give feedback.
All reactions