Autocomplete (IntelliSense) After List/Collection Includes is Broken

[AinoraZ]

Description

There is currently an issue with VS and VSCode autocomplete that leads to incorrect code suggestions for nested Includes that come after a collection Include. Specifically, this happens when the included collection implements IEnumerable<T> (ex: ICollection<T>, List<T>).

The issue is being tracked in Roslyn repository: #63108. Please like (👍) the Roslyn issue to get more attention there.

Current behaviour

Expected behaviour

Workarounds

This only affects autocomplete on VS and VSCode and only for the first include of an affected builder. The code will still compile. Regardless, it can be annoying and break the flow.

One way to circumvent this, is to manually add the relevant type to the include expression:

.UseIncludeBuilder()
.Include((Blog b) => b.Posts, builder => builder
    .Include((Post p) => p.Readers, builder => builder
        .Include((User r) => r.Posts)
    )
)
.Build()

But it looks like a proper fix can only be done by fixing the underlying Roslyn issue.