Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Colored response codes based on status code #46

Closed
liyasthomas opened this issue Aug 24, 2019 · 1 comment
Closed

Colored response codes based on status code #46

liyasthomas opened this issue Aug 24, 2019 · 1 comment
Assignees
@liyasthomas
Labels
feature New feature or request good first issue Good for newcomers

Comments

@liyasthomas
Copy link
Member

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.
@liyasthomas liyasthomas self-assigned this Aug 24, 2019
@liyasthomas liyasthomas added feature New feature or request good first issue Good for newcomers labels Aug 24, 2019
@liyasthomas liyasthomas added this to the v1.0 Stable release milestone Aug 24, 2019
@izerozlu izerozlu mentioned this issue Aug 24, 2019
Merged
@liyasthomas
Copy link
Member Author

Closing the issue since #52 solved it

AndrewBastin pushed a commit that referenced this issue Apr 11, 2023
@mirarifhasan
feat: introducing rate-limiting on queries, mutations and most of the…
fa8ca05 
… REST endpoints (HBE-111) (#46)

* feat: rate-limiting guard added and configured in app module

* feat: rate-limit annotation added in controllers and resolvers (query, mutation, not subscription)

* docs: added comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@liyasthomas liyasthomas

Labels
feature New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@liyasthomas