[GH-ISSUE #46] Colored response codes based on status code #20

Closed
opened 2026-03-16 12:48:03 +03:00 by kerem · 1 comment
Owner

Originally created by @liyasthomas on GitHub (Aug 24, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/46

Originally assigned to: @liyasthomas on GitHub.

Is your feature request related to a problem? Please describe.
It would've been great to analyse request responses if they are colored based on their status codes. Ex: green for 200, yellow for 301, red for 404 etc.

Describe the solution you'd like
Show colored responses based on its status code to easily identify the response status. Add a class name based on status code to color the status code. Preserve the same for history section.

Describe alternatives you've considered
The only way to identify status codes are manually checking them. Colored codes would help it 100x times.

Additional context
History section should also follow these colored responses for future reference. Add a string for history array to contain color class.

Originally created by @liyasthomas on GitHub (Aug 24, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/46 Originally assigned to: @liyasthomas on GitHub. **Is your feature request related to a problem? Please describe.** It would've been great to analyse request responses if they are colored based on their status codes. Ex: green for 200, yellow for 301, red for 404 etc. **Describe the solution you'd like** Show colored responses based on its status code to easily identify the response status. Add a class name based on status code to color the status code. Preserve the same for history section. **Describe alternatives you've considered** The only way to identify status codes are manually checking them. Colored codes would help it 100x times. **Additional context** History section should also follow these colored responses for future reference. Add a string for history array to contain color class.
kerem 2026-03-16 12:48:03 +03:00
Author
Owner

@liyasthomas commented on GitHub (Aug 25, 2019):

Closing the issue since #52 solved it

<!-- gh-comment-id:524591348 --> @liyasthomas commented on GitHub (Aug 25, 2019): Closing the issue since #52 solved it
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#20
No description provided.