Skip to content
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.

Consider getting rid of ActionResultsHelper #316

Closed
yishaigalatzer opened this issue Apr 25, 2014 · 1 comment
Closed

Consider getting rid of ActionResultsHelper #316

yishaigalatzer opened this issue Apr 25, 2014 · 1 comment
Labels
Milestone

Comments

@yishaigalatzer
Copy link
Contributor

(also IActionResultHelper) It started as an extensibility and convenience point. Looks not that interesting at this point.

Either we add all the helpers on it, or remove it completely

@davidfowl @loudej - thoughts

@yishaigalatzer
Copy link
Contributor Author

Chatted with @davidfowl - Will show a design (either fleshing more things in the helper, or getting rid of it).

The meta question is what is the purpose of the POCO controller

  1. Should it be easy to return views/json etc. Should we
  2. Should it be easy to return objects (like the previous try of int => status code, string => text content, Other objects => Json/Conneg, IActionResult ...
  3. Should is be easy to build another base controller without deriving from Controller

@JaneZhouQ JaneZhouQ added this to the Post Alpha milestone May 14, 2014
@yishaigalatzer yishaigalatzer removed this from the Post Alpha milestone May 23, 2014
@danroth27 danroth27 added this to the 6.0.0-alpha3 milestone Oct 15, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants