JSON Request/Response Body Syntax Color Highlighting
See original GitHub issue⚠️ Is your feature request related to a problem? Please describe
💡 Describe the solution you’d like
📊 Describe alternatives you’ve considered
📄 Additional context
🙋 Do you want to develop this feature yourself?
- Yes
- No
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (1 by maintainers)
Top Results From Across the Web
JSON Syntax Highlighting tool to helps read JSON easily
Best Online JSON syntax Highlighter to helps to view the JSON in colorful way and it's easy to understand. Support Light and Dark...
Read more >Colors and formatting - HTTPie 3.2.1 (latest) docs
Syntax highlighting is applied to HTTP headers and bodies (where it makes sense). You can choose your preferred color scheme via the --style...
Read more >Understanding JSON Schema
JSON Schema is a powerful tool for validating the structure of JSON data. However, learning to use it by reading its.
Read more >Snippet Code - Proxyman Documentation
Use JSON File as a Body of Request or Response. . Use multiple JSON files ... Use ArrayBuffer in Request/Response Body ... Comment...
Read more >response.json() - Python requests - GeeksforGeeks
response.json() returns a JSON object of the result (if the result was written in JSON format, if not it raises an error).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mertceyhan We switched from
TextView
, because we had an issue reported about poor performance on some big responses. In general, I believe that currentRecyclerView
implementation is the best solution at the moment till we switch to Jetpack Compose (when it reaches some stable state).Agree with your point on trying to distinguish key and value. This is what stopped us and other contributors so far, I guess. But I believe that there is a solution for future. Since we are going to introduce some breaking changes in
4.x
release we also have plans on redesigning database entities to have separateTransaction
,Request
andResponse
models. And in these redesigned models I thought we could change the way how we store the payload to not have just a bigString
there.So I would suggest to not spend time on this issue at the moment till we present something more suitable for such customizations.
Thanks @vbuberen. I will start looking into it and hopefully will open a pull request soon.