[GH-ISSUE #3887] [feature]: HTML Entity Encoding #1366

New issue

Open

opened 2026-03-16 20:00:28 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 20:00:28 +03:00

Owner

Originally created by @Whtfck on GitHub (Mar 11, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3887

Is there an existing issue for this?

I have searched the existing issues

Summary

Using Hoppscotch to access an API, the response I receive is encoded with HTML entities. I would like the response result to be post-processed using a JavaScript script. When receiving the response, I want the script to execute first and then display the result. Alternatively, it could automatically decode HTML entities.

Why should this be worked on?

Because if the response message cannot be decoded, it's impossible to determine the content of the message. Consequently, one would need to copy the message to an online encoding and decoding platform for translation, which undeniably adds a significant amount of work.

Originally created by @Whtfck on GitHub (Mar 11, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3887 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary Using Hoppscotch to access an API, the response I receive is encoded with HTML entities. I would like the response result to be post-processed using a JavaScript script. When receiving the response, I want the script to execute first and then display the result. Alternatively, it could automatically decode HTML entities. ![Snipaste_2024-03-11_10-16-51](https://github.com/hoppscotch/hoppscotch/assets/101028256/0f85b7b9-bb6d-4cc5-a008-69f3bcb5fb87) ### Why should this be worked on? Because if the response message cannot be decoded, it's impossible to determine the content of the message. Consequently, one would need to copy the message to an online encoding and decoding platform for translation, which undeniably adds a significant amount of work.