My observation in ASP.NET Core 2.1 is quite the opposite of a similar question raised about string.empty being converted to null when passing JSON object to MVC Controller.
In my case, when a JSON object with properties containing empty strings is sent back to a controller, they are not automatically converted to null anymore.
For instance, consider this JavaScript object:
var person = {firstName:"", lastName:""};
$http.post("/app/index", person)
.then(function (response) {
// Success
}, function (error) {
// Failure
})
Upon binding to the model in the controller, the properties with empty strings remain as such:
//
// POST: /App
[HttpPost]
public async Task<ActionResult> Index([FromBody] AppFormDTO data)
{
....
}
When attempting to save this object in the database, it would be preferable to have null values instead of numerous empty strings.
Has there been a change to the DefaultModelBinder in ASP.NET Core 2.1? If so, how can I revert it back to the behavior in MVC5 where string.empty was automatically converted to null?
UPDATE, including my AppFormDTO model for reference:
public class AppFormDTO
{
public string firstName{ get; set; }
public string lastName{ get; set; }
}