[GH-ISSUE #206] Display sendRequest runtime errors in the console #78

New issue

Closed

opened 2026-03-16 13:13:08 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 13:13:08 +03:00

Owner

Originally created by @nickpalenchar on GitHub (Oct 23, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/206

Originally assigned to: @nickpalenchar on GitHub.

Currently only a specific type of error caught in sendRequest is displayed. All others are swallowed, but the message displayed to the users instructs to check the console for errors. Let's show those errors appropriately so that the resolve makes sense.

Originally created by @nickpalenchar on GitHub (Oct 23, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/206 Originally assigned to: @nickpalenchar on GitHub. Currently only a specific type of error caught in sendRequest is displayed. All others are swallowed, but the message displayed to the users instructs to check the console for errors. Let's show those errors appropriately so that the resolve makes sense.

kerem closed this issue

2026-03-16 13:13:13 +03:00

kerem commented

2026-03-16 13:13:19 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 23, 2019):

Thats better! Perhaps show a toast? Than console.log().

this.$toast.error(error.response + error.code, {
 icon: 'error'
});

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status

@liyasthomas commented on GitHub (Oct 23, 2019): Thats better! Perhaps show a toast? Than console.log(). ``` this.$toast.error(error.response + error.code, { icon: 'error' }); ``` https://developer.mozilla.org/en-US/docs/Web/HTTP/Status

kerem commented

2026-03-16 13:13:24 +03:00

Author

Owner

@nickpalenchar commented on GitHub (Oct 23, 2019):

Toast would be good. Looking at a why-not-have both approach. Toast would display the error message but having the full error in the console is also good to easily refer to, as well as getting more verbose details like the error stack (this is being implemented as a console.error rather than console log)

@nickpalenchar commented on GitHub (Oct 23, 2019): Toast would be good. Looking at a why-not-have both approach. Toast would display the error message but having the full error in the console is also good to easily refer to, as well as getting more verbose details like the error stack (this is being implemented as a console.error rather than console log)

kerem commented

2026-03-16 13:13:29 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 23, 2019):

Yeah! That's correct. Just saw the branch. Make the PR. Will merge right away!

@liyasthomas commented on GitHub (Oct 23, 2019): Yeah! That's correct. Just saw the branch. Make the PR. Will merge right away!

kerem referenced this issue

2026-03-17 00:06:20 +03:00

[PR #78] [CLOSED] Syntax Highlighting for HTML, CSS, JS, XML, JSON and SVG #2400