Skip to content
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

Public API changes to QueryMethodProvider #17153

Merged
merged 1 commit into from
Aug 15, 2019

Conversation

roji
Copy link
Member

@roji roji commented Aug 14, 2019

No description provided.

@roji roji merged commit 9186d45 into release/3.0 Aug 15, 2019
@ghost ghost deleted the QueryMethodsIsSoMuchShorter branch August 15, 2019 00:23
=> methodInfo.IsGenericMethod
&& AverageWithSelectorMethods.Values.Contains(methodInfo.GetGenericMethodDefinition());

public static IReadOnlyDictionary<Type, MethodInfo> SumWithoutSelectorMethods { get; }
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't we decide to expose method to get method info for particular type rather than whole dictionary?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes--I missed this in my review. @roji?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, sorry, I thought we said changing to read-only is enough - there could conceivable be some value in allowing users to iterate over the keys/values. But I can of course change this if you guys prefer a get method (GetSumWithoutSelector?)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't feel strongly about it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Convert to method which takes type. Current usages does not require iterating over values. We could add dictionary later if situation requires it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants