CSHARP-4935 allow Linq Translation conversion from interface to deriv… #1250
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.
…ed type.
This will allow for a proper "downcasing" of the type. With my proposed changes we will now be able to run filters if the collection type is an interface.
I also had to change the default implementation of how the DiscriminatedInterfaceSerializer works as there would always be an exception as the object serializer enforces a whitelist for types to be serialized. I would actually like it better if we would instead resolve the class map of the underlying type to serialize a dependent object, but I did not want to touch on this in this PR.
I am unsure about the placement of the ConvertExpressionToFilterTranslatorTest as it is a bit different to the other tests in that file, but it was the only way to trigger the conversion in ConvertExpressionToFilterFieldTranslator