I am consuming a service that has the following definition:
[HttpGet]
[SwaggerOperation(nameof(GetAnimal))]
[Route("{animalId:long}", Name = nameof(GetAnimal))]
[ProducesResponseType(typeof(AnimalModel), StatusCodes.Status200OK)]
[ProducesResponseType(typeof(ErrorModel), StatusCodes.Status500InternalServerError)]
public Task<IActionResult> GetAnimal(string tenantId, long animalId)
{
try
{
// Find the actual animal.. somewhere.
return Ok(new AnimalModel());
}
catch (Exception exception)
{
return InternalServerError(new ErrorModel());
}
}
This seems to cause autorest
to generate a C# client with an object
as a return type (I guess because of the ProducesResponseType
attribute being specified twice):
public async Task<HttpOperationResponse<object>> GetAnimalWithHttpMessagesAsync(string tenantId, long animalId, [..])
Question
What is the recommended way to handle an API that return different objects?
Potential solutions
AnimalModel
and the ErrorModel
(could be better).ASP.NET Core 2.1 introduces the
ActionResult<T>
return type for Web API controller actions. It enables you to return a type deriving fromActionResult
or return a specific type.ActionResult<T>
offers the following benefits over theIActionResult
type:
- The
[ProducesResponseType]
attribute'sType
property can be excluded. For example,[ProducesResponseType(200, Type = typeof(Product))]
is simplified to[ProducesResponseType(200)]
. The action's expected return type is instead inferred from theT
inActionResult<T>
.- Implicit cast operators support the conversion of both
T
andActionResult
toActionResult<T>
.T
converts toObjectResult
, which meansreturn new ObjectResult(T);
is simplified toreturn T;
.
Consider using the new ActionResult<T>
and remove the produces response attribute
Type
altogether.
[HttpGet]
[SwaggerOperation(nameof(GetAnimal))]
[Route("{animalId:long}", Name = nameof(GetAnimal))]
[ProducesResponseType(StatusCodes.Status200OK)]
[ProducesResponseType(StatusCodes.Status500InternalServerError)]
public async Task<ActionResult<AnimalModel>> GetAnimal(string tenantId, long animalId) {
try {
// Find the actual animal.. somewhere...using await.
var model = new AnimalModel();
//populate model
return model;
} catch (Exception exception) {
return InternalServerError(new ErrorModel());
}
}