.NET EF Core 模型的 6 个可为 null 的属性警告

Question

I'm using EF Core, and I have this model:

public class Article
{
    public int Id { get; set; }
    public User Author { get; set; } // <- CS8618
    public int AuthorId { get; set; }
}

As pointed out in the above code comment, I get an annoying nullable warning. I'm using the Fluent API to annotate my model, and obviously Author is not nullable as AuthorId is not nullable.

I feel that using User? Author User? Author instead to make the warning go away is incorrect, as the property is obviously not nullable, and it would be a lie, and also a hint to people using my model that it is nullable.

What is the proper way to deal with this situation? Suppress the warning?

Answer 1

You'd find a lot of different answers on this question

But in this particular case, I would ask myself the question: who generates instances of this class?

1a

If you are 100% relying on EF Core to generate instances of this class for you by querying the database, and you are 100% sure that you ALWAYS use the proper Include() , I would safely set the Author field to null! , which means it assigns the default value null on construction and automatically suppresses the nullability error.

public class Article
{
    public int Id { get; set; }
    public User Author { get; set; } = null!;
    public int AuthorId { get; set; }
}

1b

You could also use the above solution with a private constructor to protect that no-one else but EF Core will generate instances of this class.

public class Article
{
    private Article()
    {
        Author = null!;
    }

    public int Id { get; set; }
    public User Author { get; set; }
    public int AuthorId { get; set; }
}

2

If you generate instances of this class in any other parts of your code, you would need a constructor to ensure that Author is never null after construction.

public class Article
{
    public Article()
    {
        Author = new User();
    }

    public int Id { get; set; }
    public User Author { get; set; }
    public int AuthorId { get; set; }
}

3

If you do not allow a default User object, it would make sense to expect a null value for Author but mark it Required to ensure that it will never be null when written to database.

public class Article
{
    public int Id { get; set; }

    [Required]
    public User? Author { get; set; }
    public int AuthorId { get; set; }
}

Answer 2

只需将“#nullable disable”放在命名空间上方即可。

Answer 3

Since C#11 ( .NET 7.0 ) you can add a required modifier.

public class Article
{
    public int Id { get; set; }
    public required User Author { get; set; }
    public int AuthorId { get; set; }
}

And with the required modifier, you won't be able to use var article= new Article(); to create an object instance. So it's great protection for the not nullable property User .

Now to create an object instance you must do something like:

var article= new Article()
{
   User = new();
};

Originally answer was posted on: What is best way to create .NET6 class with many non-nullable properties?

More detailed info: https://learn.microsoft.com/en-us/do.net/csharp/language-reference/keywords/required