Null destination value type with mapper#3458
Conversation
408adb0 to
484826b
Compare
| @@ -1 +1,6 @@ | |||
| Total Issues: 0 | |||
| Compat issues with assembly AutoMapper: | |||
| InterfacesShouldHaveSameMembers : Interface member 'public void AutoMapper.IConfigurationProvider.Validate(AutoMapper.ValidationContext)' is present in the contract but not in the implementation. | |||
There was a problem hiding this comment.
I don't see why anyone would call this. I guess I made it public just because there is no clear separation between the public API and the internal API.
There was a problem hiding this comment.
Regardless, this will require a major version change if we break these contracts.
There was a problem hiding this comment.
I disagree. Some things are public just because they might be useful from outside, they are not part of the API. While I'm not against releasing only major versions, it's not sending the right message, right? :) If people use this stuff, they'll break, but this seems better than not being able to do stuff at all.
There was a problem hiding this comment.
I think we should simply review what API Compat finds and make a judgement call. In this particular case, it seems simple enough.
6db55ad to
2835737
Compare
98cd6a5 to
03374e9
Compare
2599fe2 to
5275638
Compare
9a8242f to
b8f6cd9
Compare
c1cc8ed to
1da0585
Compare
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Fixes #3486. Fixes #3496.