Add IResult implementations for more IActionResults

[halter73]

Currently, only JsonResult and StatusCodeResult implement both an IActionResult and IResult. This means there are a bunch of remaining built-in IActionResults implementations that have no IResult equivalent.

• ContentResult
• VirtualFileResult
• PhysicalFileResult
• FileStreamResult
• FileContentResult
• RedirectResult
• LocalRedirectResult
• ChallengeResult
• ForbidResult
• SignIn/OutResult
• RedirectToAction/PageResult?
• ObjectResult?

ObjectResult is the big IActionResult that probably doesn't have an easy IResult implementation. I feel this requires some support for content-negotiation, but maybe we can just assume JSON.

[davidfowl]

@pranavkm should we bother with ActionResult<T>?

[halter73]

We should think how ActionResult<T> plays with the OpenAPI definition. #30662 @jkotalik

[davidfowl]

We'll strike out the action results that don't make sense once we investigate their feasibility

[halter73]

For anyone looking at this because of the help-wanted label, feel free to take a subset of these types. I have a feeling something like RedirectResult will be easier to chew off than ObjectResult.

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[uabarahona]

Sounds interesting, I will take the easiest ones 😄

[deepumi]

I would like to try ContentResult or something simple.