From 312ece61bf3332025468f747a2aeb33914b083d9 Mon Sep 17 00:00:00 2001 From: Matthias <121162196+Gre210675@users.noreply.github.com> Date: Wed, 10 Dec 2025 13:31:34 +0100 Subject: [PATCH] Fix typo in mapping-attributes.md --- .../core/modeling/relationships/mapping-attributes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/entity-framework/core/modeling/relationships/mapping-attributes.md b/entity-framework/core/modeling/relationships/mapping-attributes.md index 5f553c8ef1..6d5fe39f11 100644 --- a/entity-framework/core/modeling/relationships/mapping-attributes.md +++ b/entity-framework/core/modeling/relationships/mapping-attributes.md @@ -45,7 +45,7 @@ The use of data annotations across many technologies and for both mapping and va [!code-csharp[RequiredOnForeignKey](../../../../samples/core/Modeling/Relationships/MappingAttributes.cs?name=RequiredOnForeignKey)] > [!NOTE] -> When using [C# nullable reference types](/dotnet/csharp/tutorials/nullable-reference-types), the `BlogId` property in this example is already non-nullable, which means the `[Required]` attribute will have no affect. +> When using [C# nullable reference types](/dotnet/csharp/tutorials/nullable-reference-types), the `BlogId` property in this example is already non-nullable, which means the `[Required]` attribute will have no effect. `[Required]` placed on the dependent navigation has the same effect. That is, making the foreign key non-nullable, and thereby making the relationship required. For example: