inspector: migrate errors from C++ to JS #19387
Conversation
targos
added
inspector
nodejs-github-bot
added
c++
targos
added
the
semver-major
doc/api/errors.md
Outdated
| ### ERR_INSPECTOR_ALREADY_ATTACHED | ||
|
|
||
| While using the `inspector` module, an attempt was made to connect a session | ||
| when another session was already attacheds. |
targos
force-pushed
the
error-codes-inspector
branch
from
2faae1f to
38a566e
Compare
doc/api/errors.md
Outdated
| <a id="ERR_INSPECTOR_ALREADY_ATTACHED"></a> | ||
| ### ERR_INSPECTOR_ALREADY_ATTACHED | ||
|
|
||
| While using the `inspector` module, an attempt was made to connect a session |
There was a problem hiding this comment.
Should this reuse the ERR_INSPECTOR_ALREADY_CONNECTED instead of creating a new error? From what I can tell, the only distinction is that if you connect from the same session twice, you get an ERR_INSPECTOR_ALREADY_CONNECTED, whereas if you connect from another session, you get an ERR_INSPECTOR_ALREADY_ATTACHED, but the cause are the same: there is a current connected session, whether it's the same one or a different one does not seem to make a big difference.
To get out of ERR_INSPECTOR_ALREADY_CONNECTED, the user can call.disconnect(), but there is not a method called .detach() that a user can use to get out of ERR_INSPECTOR_ALREADY_ATTACHED, they still need to .disconnect() to detach - and there is no explanation about attach in the inspector documentation. IMO the difference should probably be told in the error message, not in the code, so it's [ERR_INSPECTOR_ALREADY_CONNECTED]: the inspector session is already connected v.s. [ERR_INSPECTOR_ALREADY_CONNECTED]: another inspector session is already connected
There was a problem hiding this comment.
Good point. I'm going to change this.
Assign a code to a user-facing error. Turn other internal-only errors to checks.
targos
force-pushed
the
error-codes-inspector
branch
from
38a566e to
c08f887
Compare
|
Updated. New CI: https://ci.nodejs.org/job/node-test-pull-request/13796/ |
|
CI is green. Is everyone OK with @joyeecheung's suggestion? |
|
Landed in 4e1f090 |
Assign a code to a user-facing error. Turn other internal-only errors to checks. PR-URL: #19387 Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Eugene Ostroukhov <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
Assign a code to a user-facing error.
Turn other internal-only errors to checks.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes