Downstream dependencies have issues surfaced by yarn audit
The repo doesn't have release notes (that I could find), but looking at the commits since 1.5.0 they're all bumping deps and messing with CI
Depends on D3858
Differential D3859 Authored by atul on Apr 27 2022, 8:12 AM.
Details
Summary Downstream dependencies have issues surfaced by yarn audit The repo doesn't have release notes (that I could find), but looking at the commits since 1.5.0 they're all bumping deps and messing with CI Depends on D3858 Test Plan CI
Diff Detail
Event TimelineHerald added subscribers: • abosh, • karol, • adrian, ashoat. · View Herald TranscriptApr 27 2022, 8:12 AM2022-04-27 08:12:29 (UTC-7) Harbormaster completed remote builds in B8605: Diff 11989.Apr 27 2022, 8:17 AM2022-04-27 08:17:24 (UTC-7) atul edited the summary of this revision. (Show Details)Apr 27 2022, 8:18 AM2022-04-27 08:18:12 (UTC-7) Harbormaster completed remote builds in B8606: Diff 11990.Apr 27 2022, 8:19 AM2022-04-27 08:19:56 (UTC-7) atul added a child revision: D3861: [keyserver] Bump `geoip-lite` to `1.4.5`.Apr 27 2022, 8:32 AM2022-04-27 08:32:41 (UTC-7) atul added a child revision: D3861: [keyserver] Bump `geoip-lite` to `1.4.5`.Apr 27 2022, 10:15 AM2022-04-27 10:15:53 (UTC-7) Comment Actions Please make sure to make me a blocking reviewer on diffs that affect dependencies in the future At some point in the future we should move this to Nix This revision is now accepted and ready to land.Apr 27 2022, 2:32 PM2022-04-27 14:32:23 (UTC-7) Comment Actions
Will do
As in include clang-format binary directly instead of sourcing from npm package? Comment Actions
Yeah Harbormaster completed remote builds in B8665: Diff 12062.Apr 28 2022, 12:10 PM2022-04-28 12:10:33 (UTC-7) Closed by commit rCOMM83dab868f3bb: [yarn] Bump `clang-format` to `1.7.0` (authored by atul). · Explain WhyApr 28 2022, 12:22 PM2022-04-28 12:22:27 (UTC-7) This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 11990 package.json
yarn.lock
|
You don't need to use React.useMemo(...) here.
The useMemo() hook is helpful for maintaining referential equality so that objects will be considered "shallowly equal" (== in JS) and we can avoid re-renders. This is helpful for objects (including Map(), Set(), etc), arrays (which are objects), and functions (which are objects).
On the other hand, strings in JS are considered shallowly equal if they have the same contents, so we don't have to worry about re-renders if the "content" stays the same.
See below:
(In like C++, which you've been working w/ recently, std::strings can be allocated on the heap (unlike integers, booleans, etc) which may have been part of your reasoning that shallow equality would check reference instead of contents?)