[lib] Naively update `threadInfoFromRawThreadInfo` to support `RawThreadInfo` argument
ClosedPublic
Actions

Authored by atul on Dec 11 2023, 3:00 AM.

Details

Reviewers

ashoat
ginsu
tomek
rohan

Commits

rCOMMe87c28f8156f: [lib] Naively update `threadInfoFromRawThreadInfo` to support `RawThreadInfo`…

Summary

This will definitely be tidied up in subsequent diff or after rebasing... but this unblocks some keyserver work that I wanted to go ahead and put up ASAP.

Depends on D10284

Test Plan

CI/flow/etc.

Diff Detail

Repository

rCOMM Comm

Branch

master

Lint

No Lint Coverage

Unit

No Test Coverage

Event Timeline

atul created this revision.Dec 11 2023, 3:00 AM

atul published this revision for review.Dec 11 2023, 3:02 AM

Harbormaster completed remote builds in B24931: Diff 34465.Dec 11 2023, 3:19 AM

atul added a child revision: D10286: [keyserver] Update `rawThreadInfoFromServerThreadInfo` to support `minimallyEncodePermissions` option.Dec 11 2023, 3:22 AM

atul mentioned this in D10235: [lib] Update `getRelativeMemberInfos` to handle both `MinimallyEncoded` and `Legacy` variants.Dec 11 2023, 5:39 PM

ashoat accepted this revision.Dec 11 2023, 7:18 PM

ashoat added inline comments.

lib/shared/thread-utils.js
899	I don't think this counts as "ridiculous" branching. It's necessary because there are indeed differences in the two, such as `getCurrentUser` vs. `getMinimallyEncodedCurrentUser` Nit, but can you maybe remove "ridiculous" here?