Provide ability to obtain expand specification on expression with reflection provider.
People seem to be using the reflection provider with custom queryable data sources that overlay custom data access layers. A common downside to this approach is the absense of $expand specifications due to the assumption of lazy loading on navigation properties. The result is that the custom queryable implementations never have a chance to expand navigation properties for the query unless their entities/domain objects truly support lazy loading, which is not always the case.
A common suggestion is to implement a custom service provider, which will hand off the full expression without any assumptions. For those of us that are interested in utilizing the reflection provider to still describe the shape of our data and not duplicating it in our own custom data provider it would be useful to have the ability to specific that the reflection provider use either eager or lazy loading in some way shape or form, and in the case of eager loading allow the full expression with $expand criteria to be passed along for evaluation.