Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(client): Force result extensions to log correct properties #16542

Merged
merged 1 commit into from Dec 1, 2022

Conversation

SevInf
Copy link
Contributor

@SevInf SevInf commented Nov 30, 2022

Node.js util.inspect and console functions deliberately avoid
triggering any of the proxy traps. If result extensions are used, that
forces us to show completely incorrect result - it will show the target
which would not match what user is actually getting there.

Fix #16554

@SevInf SevInf requested review from a team and aqrln and removed request for a team November 30, 2022 11:58
@SevInf SevInf added this to the 4.8.0 milestone Nov 30, 2022
@SevInf SevInf force-pushed the log-proxy branch 2 times, most recently from 9334ae6 to b048a7c Compare November 30, 2022 12:06
Copy link
Member

@aqrln aqrln left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice!

@SevInf SevInf force-pushed the log-proxy branch 2 times, most recently from fd863da to 9b7c830 Compare November 30, 2022 13:14
Node.js `util.inspect` and console functions deliberately avoid
triggering any of the proxy traps. If result extensions are used, that
forces us to show completely incorrect result - it will show the target
which would not match what user is actually getting there.
@SevInf SevInf merged commit 73a5ffe into main Dec 1, 2022
@SevInf SevInf deleted the log-proxy branch December 1, 2022 09:15
SevInf added a commit that referenced this pull request Dec 1, 2022
)

Node.js `util.inspect` and console functions deliberately avoid
triggering any of the proxy traps. If result extensions are used, that
forces us to show completely incorrect result - it will show the target
which would not match what user is actually getting there.
jkomyno pushed a commit that referenced this pull request Dec 21, 2022
)

Node.js `util.inspect` and console functions deliberately avoid
triggering any of the proxy traps. If result extensions are used, that
forces us to show completely incorrect result - it will show the target
which would not match what user is actually getting there.
jkomyno pushed a commit that referenced this pull request Dec 21, 2022
)

Node.js `util.inspect` and console functions deliberately avoid
triggering any of the proxy traps. If result extensions are used, that
forces us to show completely incorrect result - it will show the target
which would not match what user is actually getting there.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

console.log outputs incorrect value when result extensions are used
3 participants