-
Notifications
You must be signed in to change notification settings - Fork 214
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
Patch vega d3 fix fixme #2575
Patch vega d3 fix fixme #2575
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had no idea this patch mechanism existed. I don't know whether to be pleased or horrified by it, but in any case I'm glad to see this particular set of problems fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I understand this. But you might do well to stand by for reviews from others who are more confident.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, after the behaviour changes are fixed.
Found and patched where vega-util was overriding
Object.constructor
by assignment.Fixing that uncovered same problem with d3-color. Same patch.
vega-util was also overriding two other frozen primordial properties by assignment,
hasOwnProperties
andtoString
. Patched both, althoughtoString
is a hopeless cause. But fixinghasOwnProperties
means SES can stop enabling it, further reducing vscode debugger's object inspector noise.Fixes #2556
Fixes the FIXME kludge added to bin/runner at
https://github.com/Agoric/agoric-sdk/pull/2552/files/84f9ccf388e6aeb71b5aabb2a552e5ec36d4fa9f#r585869497
See
vega/vega#3075
endojs/endo#576