mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #2877] [feature]: Prettify response #927
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#927
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @marc0l92 on GitHub (Dec 12, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2877
Is there an existing issue for this?
Summary
When I call a JSON api that replies with a minified JSON it is really difficult to read the response.

I would be useful to have a prettify feature for the response:
Why should this be worked on?
Increase readability of API responses without using external tools to prettify the JSON.
@anwarulislam commented on GitHub (Dec 25, 2022):
@marc0l92 Currently, we prettify JSON before rendering it. There might be an issue with the JSON object when we try to stringify it with space.
@anwarulislam commented on GitHub (Dec 25, 2022):
@AndrewBastin I have checked this.
LJSON.parse()method is not working with this specific object. But, when I useJSON.parse()it works.@harish343 commented on GitHub (Feb 18, 2023):
how can i start work on this issue
@liyasthomas commented on GitHub (Feb 18, 2023):
Hi @harish343, you can look into this feature request.
@jaysoni-ash42 commented on GitHub (Apr 19, 2023):
@liyasthomas tried locally updating the lossless-json package version to 2.0.8 resolves this parsing issue.