[lib] Fix incorrect timestamps for sidebars
AcceptedPublic
Actions

Authored by ashoat on Wed, Nov 20, 9:04 AM.

Details

Reviewers

varun
will

Summary

This addresses ENG-9951:

Fixes useSidebarInfos's initial ordering to sort on lastUpdatedAtLeastTime (a number) instead of lastUpdatedTime (a promise). Flow failed to catch this because Lodash's usage is hard to type.
Fixes lastUpdatedTimeIncludingSidebars to consider all sidebars, instead of trusting the first one in the initial order to have the most recent timestamp.
Fixes getAllFinalSidebarItems to reorder after all promises resolve.

Test Plan

Tested on both native (my iOS device running a Release build pointed at prod) and web (my comm.software staging environment that uses prod data)

Diff Detail

Repository

rCOMM Comm

Branch

ashoat/fix

Lint

No Lint Coverage

Unit

No Test Coverage

Event Timeline

ashoat created this revision.Wed, Nov 20, 9:04 AM

Herald added a subscriber: tomek. · View Herald TranscriptWed, Nov 20, 9:04 AM

ashoat published this revision for review.Wed, Nov 20, 9:08 AM

Harbormaster completed remote builds in B32739: Diff 45913.Wed, Nov 20, 9:28 AM

will accepted this revision.Wed, Nov 20, 3:36 PM

This revision is now accepted and ready to land.Wed, Nov 20, 3:36 PM

Changes in initial version broke useSearchSidebars comparison algo. Moved the sorting to getSidebarItems instead, which isn't used in useSearchSidebars and is only used in chat-selectors.js

Harbormaster completed remote builds in B32740: Diff 45914.Wed, Nov 20, 7:34 PM