PropertyBuilder can have custom ValueComparer #19256
Closed
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.
I have a DbContext with a conversion like this:
When the DbContext gets created, it logs the following warning:
Apparently there is no ValueComparer associated with this property. Only InternalPropertyBuilder allowed setting custom ValueCompareres. I though it was a good idea to allow custom ValueComparers to get rid of the mentioned warning. What do you think?