More flexible Include API - allow walking back up include tree
I like the Include().ThenInclude() syntax of EF Core. It would also be great if there was an "AlsoInclude" so that when you want to include another peer several levels deep, you don't have to start at the top (with Include) again. You start getting these really long statements with many include, then include, then include (back to) include, then include, then include, then include, etc. Not a big deal or nothing. It works as is, but syntactically could certainly be more readable if we had a peer level include (ie, whatever entity was "above" the last ThenInclude). Does that make sense?
Posted by JeffGillin on Feb 4, 2016, 3:23 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
More flexible Include API - allow walking back up include tree
I like the Include().ThenInclude() syntax of EF Core. It would also be great if there was an "AlsoInclude" so that when you want to include another peer several levels deep, you don't have to start at the top (with Include) again. You start getting these really long statements with many include, then include, then include (back to) include, then include, then include, then include, etc. Not a big deal or nothing. It works as is, but syntactically could certainly be more readable if we had a peer level include (ie, whatever entity was "above" the last ThenInclude). Does that make sense?
Comments (0)
No comments yet. Start the discussion.