-
Notifications
You must be signed in to change notification settings - Fork 243
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
SelectMany option for Specification<T, TResult> #294
Comments
I'm hitting a major performance issue. I'm currently querying an aggregate and its entities, but the DbContext is getting bloated and causing slow performance. My thought was to write two specs, one that queries the aggregate with I could ditch |
Hi, Yea, it would be great. Wanna give it a shot? @MGramolini ? It's a bit of a problem though. Users might think that they can chain multiple Also, if you used |
If someone wants to take on adding SelectMany support to the library, we're open to a pull request for it! |
I also have a need for SelectMany. I haven't seen any traffic on this for a while, so I'm willing to attempt a PR if no one else has started work on this. |
Any plans for a release in the near future with thsi feature? |
Yes, in the next two weeks, around 15th May. |
Closing the issue, the feature is published in version 7. |
It would be useful to be able to do a SelectMany and I believe it would not take much effort to add. I would be willing to make the adjustments if it would be considered.
The text was updated successfully, but these errors were encountered: