8000 util: make sure error causes of any type may be inspected by BridgeAR · Pull Request #41097 · nodejs/node · GitHub
[go: up one dir, main page]

Skip to content

Conversation

@BridgeAR
Copy link
Member
@BridgeAR BridgeAR commented Dec 6, 2021

An error cause may be of any type. Handle all of them, no matter
if they are an error or not.

Fixes: #41096

Signed-off-by: Ruben Bridgewater ruben@bridgewater.de

@BridgeAR BridgeAR requested a review from targos December 6, 2021 13:34
@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. util Issues and PRs related to the built-in util module. labels Dec 6, 2021
@targos
Copy link
Member
targos commented Dec 6, 2021

I also found that falsy causes are not inspected, but that can be fixed in a separate PR.

@BridgeAR
Copy link
Member Author
BridgeAR commented Dec 6, 2021

@targos how would you handle undefined and null? I would at least skip those?

@targos
Copy link
Member
targos commented Dec 6, 2021

I would always inspect if Object.hasOwn(err, 'cause') === true with no exception.

@BridgeAR
Copy link
Member Author
BridgeAR commented Dec 6, 2021

@targos I added another commit to also inspect falsy values besides undefined. Undefined is used in argument default values as "does not exist" and I would handle it here identically.

An error cause may be of any type. Handle all of them, no matter
if they are an error or not.

Fixes: nodejs#41096

Signed-off-by: Ruben Bridgewater <ruben@bridgewater.de>
Signed-off-by: Ruben Bridgewater <ruben@bridgewater.de>