-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to set provider value comparer when configuring value conversion #27738
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
regression
type-enhancement
Milestone
Comments
AndriySvyryd
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
May 3, 2022
AndriySvyryd
added a commit
that referenced
this issue
May 3, 2022
AndriySvyryd
added a commit
that referenced
this issue
May 5, 2022
Use client value comparer as provider value comparer if possible The client value comparer will not be used if the model type is a nullable value type since we need the types to match exactly and the provider type is never nullable Fix some API issues Remove some unused code Fixes #27738 Fixes #27850 Fixes #27791 Part of #27588
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
regression
type-enhancement
This would allow to use case-insensitive comparison for example.
Consider showing a warning when an FK or PK property has a custom value comparer but provider value comparer is not specified
The text was updated successfully, but these errors were encountered: