Supporting comparison to null in Filter expression #204
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes NullFilter & NotNullFilter tests.
Newton soft converters are based upon the abstract value & reference type converters, which are not built to expect Nullable<T> values (which are nullable, but are also value types)
mfenniak
added a commit
that referenced
this pull request
Apr 14, 2015
Supporting comparison to null in Filter expression
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR addresses the reported issue #203, where comparison with null doesn't work correctly in Filter clauses. There are three general cases that support were added for; comparing a Nullable<T> to null, comparing a reference type to null, and using Nullable<T>.HasValue.