You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the HtmlMediaTypeViewformatter should not try to serialize the HttpError type and leave it to other formatters (maybe the default ones) to deal with this.
Another option would be to provide an 'out-of-the-box' view for HttpError, which would display nicely the errors in the same fashion the MVC projects.
This is to avoid creating a boilerplate HttpError view for every project suing the html formatter. I can work on this, but I'd like to hear your input first before getting started.
Thanks!
The text was updated successfully, but these errors were encountered:
Yes, that would be great! Sorry for the delay in replying. I only just saw this comment. We are currently discussing a re-merge of projects since the initial goal of independent maintainers was never realized, and that should help with managing issues better.
I think the
HtmlMediaTypeViewformatter
should not try to serialize theHttpError
type and leave it to other formatters (maybe the default ones) to deal with this.Another option would be to provide an 'out-of-the-box' view for HttpError, which would display nicely the errors in the same fashion the MVC projects.
This is to avoid creating a boilerplate HttpError view for every project suing the html formatter. I can work on this, but I'd like to hear your input first before getting started.
Thanks!
The text was updated successfully, but these errors were encountered: