"Navigating and including nullable relationships" example

[uecasm]

Console.WriteLine(order.OptionalInfo!.ExtraAdditionalInfo!.SomeExtraAdditionalInfo);

This example is cited in a section that talks about nullable navigations not needing explicit null checks in the context of LINQ to EF queries, because the null checks are implied by the query rewrite. But the above code is not in that context, and it seems entirely reasonable for any of those optional properties to actually be null (and thus inappropriate to use the ! operator), absent some additional context (such as order being the result of a query that did already verify all those properties).

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 93c3721a-da23-d9ea-a054-9d786d2ff4d2
• Version Independent ID: 6d3b0f96-6642-75e5-93c8-02c23f142ac4
• Content: Working with nullable reference types - EF Core
• Content Source: entity-framework/core/miscellaneous/nullable-reference-types.md
• Product: entity-framework
• Technology: entity-framework-core
• GitHub Login: @roji
• Microsoft Alias: avickers

[roji]

Thanks, makes sense - I've changed the sample to show an explicit query to make this clear.