-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Body Response in HTML #3
Comments
Okay, I will consider to implement this. |
I had a bash at showing the rendered HTML in the "Response Body with Syntax Highlight" tab on my fork. I'm not sure it's the right place for it to be displayed and I've restricted what the content can do quite a bit. |
Excellent ! I just tested your fork with the HTML and it's working great ! |
@stiak: |
@chao: I tried adding another tab for viewing the response image. It gets a little confusing trying to find the output as one of the tabs is always empty. Maybe we could update the tab label based on the response type? That way if you're using a service that returns, say, JSON when successful or HTML on errors you can leave the same tab open and see a nicely formatted result regardless of how the request went. So default label would be "Response Body with Syntax Highlight", any image would cause it to rename to "Image" and a html response would be "Rendered HTML". Any thoughts? |
That's a good idea ! |
@stiak: I think that's a great idea, maybe the UI could be looked like fiddler2 (see: http://www.fiddler2.com/Fiddler2/images/syntaxview.png). Except we only need to show related tabs according to different content-type. For example: show tab "Header", "TextView", "SyntaxView" and "WebView" for "text/html". |
Hi guys I'm going to close this issue. |
Hello, I wanted to submit a request, but I found only the bug part available.
Would it be possible to activate a tab to see the "Body Response" in HTML.
I am using your plugin for a REST application using DJANGO framework. When an error occurs in django the Body Response is a HTML page that explains the ERROR.
Currently I need to copy paste the HTML content, to a HTML Editor to be able to read the ERROR.
The text was updated successfully, but these errors were encountered: