Igor Tkachev

/azp run test-all

/azp run test-all

You cannot use it in this way as `IQueryable` does not have any info about original object at runtime. But you can use your interfaces with generics as follows ```c#...

> I don't like this API. UseOptions may change data provider on the fly and probably has a lot of other sideeffects. If you need some specific feature, we can...

Introducing a separate Builder pattern just to restrict modifications would add unnecessary complexity. Users will need to learn yet another part of an already feature-rich API, making it harder to...

Our API is already complex enough, and we shouldn’t make it even harder to use. The proposed `UseOptions` method follows the existing options-setting API, so users don’t have to learn...

> I find that interesting, because I find the current version of the Merge API to be incredibly intuitive. The intellisense based on limited types means that the next available...

It’s not about new options. This is about modifying existing ones. The real question is: should we simply add one method that reuses the existing API, or introduce a Builder...

Added additional tests to cover all unwanted option changes.

/azp run test-all