iactionresult 图片_在操作中使用IActionResult作为结果类型的优势

What's the advantage or recommendation on using IActionResult as the return type of a WebApi controller instead of the actual type you want to return?

Most of the examples I've seen return IActionResult, but when I build my first site I exclusively use View Model classes as my return types.... now I feel like I did it all wrong!

解决方案

The main advantage is that you can return error/status codes or redirects/resource urls.

For example:

public IActionResult Get(integer id)

{

var user = db.Users.Where(u => u.UserId = id).FirstOrDefault();

if(user == null)

{

// Returns HttpCode 404

return NotFound();

}

// returns HttpCode 200

return ObjectOk(user);

}

or

public IActionResult Create(User user)

{

if(!ModelState.IsValid)

{

// returns HttpCode 400

return BadRequest(ModelState);

}

db.Users.Add(user);

db.SaveChanges();

// returns HttpCode 201

return CreatedAtActionResult("User", "Get", new { id = user.Id} );

}

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值