Fix #2852 - Support Enum.HasFlag in LINQ

[felipepessoto]

Fix #2852 - Support Enum.HasFlag in LINQ

[felipepessoto]

At first I tried to create IMethodCallTranslator, but it never get called, because the argument type of Enum.HasFlag() is a System.Enum, and it's not mapped to any CLR type.
So, I changed to IExpressionFragmentTranslator

[smitpatel]

@divega , @rowanmiller - Are we looking to take this one in?

[divega]

@smitpatel we discussed moving it to the 1.0.1 milestone in triage.

[rowanmiller]

@fujiy you probably already got this from @divega's comment - but given where we are in the 1.0.0 release, we are going to hold off on taking this and ship it in the following release (tentatively 1.0.1). We'll merge your PR once we branch for the 1.0.0 release.

[felipepessoto]

Ok. Thanks!

[rowanmiller]

@smitpatel you are good to take a look at this now (for the 1.1 release)

[smitpatel]

Derive directly from IMethodCallTranslator

[felipepessoto]

At first I tried to create IMethodCallTranslator, but it never get called, because the argument type of Enum.HasFlag() is a System.Enum, and it's not mapped to any CLR type.
So, I changed to IExpressionFragmentTranslator

[smitpatel]

That should not cause any issue since, the argument would be either parameter or constant. For both the cases, we try to find database mapping for the underlying type (which is necessary because we need to represent the argument in SQL) and if that is non-null then translator should get called.

[smitpatel]

@fujiy - Can you update the PR according to feedback?

[felipepessoto]

I'll try again with IMethodCallTranslator. But I'm having some issues running the unit tests in Visual Studio

[smitpatel]

@fujiy - Will it fine if I use this PR as starting point and do required modification on top of it before merging?

[felipepessoto]

Ok. No problem.

I'm still having issues running the unit tests.

[smitpatel]

Completed via #6431