如何在POST上创建必需的属性，但在PUT请求上不设置

Question

Let's say I have an User model which has Email and Password properties for authentication purposes, as follows:

public class User
{
    public long Id { get; set; }
    [Required]
    public string FirstName { get; set; }
    [Required]
    public string LastName { get; set; }

    [Required]
    [EmailAddress]
    public string Email { get; set; }

    [Required]
    [DataType(DataType.Password)]
    public string Password { get; set; }
}

My goal is to make these properties required only on POST requests, but not on PUT. That is: Email and Password fields are required to create a new user. But when editing I can omit these properties. I know that this goal can be archived removing the [Required] from Email and Password and checking for these properties when POSTing, but this does not seem to be a good practice.

So, there is a more elegant solution for this use case?

Answer 1

You shouldn't use an Entity as input/output parameters. Instead, create two separate view models that represent the actions being called:

public class User
{
    public long Id { get; set; }
    [Required]
    public string FirstName { get; set; }
    [Required]
    public string LastName { get; set; }

    [Required]
    [EmailAddress]
    public string Email { get; set; }

    [Required]
    [DataType(DataType.Password)]
    public string Password { get; set; }
}

// When creating, the client cannot know the Id because it doesn't exist
public class CreateUserViewModel
{
    [Required]
    public string FirstName { get; set; }
    [Required]
    public string LastName { get; set; }

    [Required]
    [EmailAddress]
    public string Email { get; set; }

    [Required]
    [DataType(DataType.Password)]
    public string Password { get; set; }
}

// and when updating, the Id is required but not the Email nor the Password
public class UpdateUserViewModel
{
    [Required]
    public long Id { get; set; } 

    [Required]
    public string FirstName { get; set; }
    [Required]
    public string LastName { get; set; }
}

Of course, since you are creating an API, "View Model" might not make a lot of sense. You may use the Data Transfer Object (DTO) term instead.

Answer 2

One suggestion would be to use View Models. In your case, you could have a RegisterViewModel that takes all of the values from the model and then you could have an EditViewModel that doesnt include email and password. In your controller, your edit function can either replace the old values for the other field or just ignore them.

https://www.codeproject.com/Articles/1174826/Using-MVVM-in-MVC-Applications-Part