-
Notifications
You must be signed in to change notification settings - Fork 461
[DataGrid] Support for multiple IAsyncQueryExecutor registrations #2730
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
[DataGrid] Support for multiple IAsyncQueryExecutor registrations #2730
Conversation
…yExecutor registrations and returns the first supporting match.
vnbaaij
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you give an example of how and why this is handy/better
|
@vnbaaij this change allows an application to use multiple different IQueryProvider implementations instead of a single one. Suppose for instance you want to use EF Core's DataContext and DataServiceQuery for OData queries. |
|
I'm totally not up to speed on EF so don't know what DataServiceQuery does. But judging from the code this change does no do any harm. |
|
I don't have much experience of this either :-) On the other hand, it would be interesting to add a Unit Test. |
|
@dvoituron sure I'll take care of adding unit tests for this feature. |
Pull Request
📖 Description
AsyncQueryExecutorSupplier modified so it looks-up multiple IAsyncQueryExecutor registrations and returns the first one that supports the provided IQueryable items source.