-
Notifications
You must be signed in to change notification settings - Fork 29
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[flow] Update
useResolvedThreadInfo
and fix subsequent flow
issues
Summary: As mentioned in D9896, there were quite a few places where refactoring code to accept `MinimallyEncodedThreadInfo` required the `useResolvedThreadInfo` hook to be updated. Updating that hook required a bunch of changes, which in turn required even more changes, etc. There wasn't a super obvious way to break down the refactoring going into this since I was responding to `flow` issues as they surfaced, so apologize for the large diff. I **think** that the changes are straightforward enough that this is fine, but I can go back and chunk changes into separate diffs if that would make things easier to review. --- Depends on D9896 Test Plan: Trusting `flow`, but also based on feedback here: https://phab.comm.dev/D9896#inline-61685... will make sure to read through this carefully a couple times and ensure the "base type(s)" and "minimally encoded type(s)" match up. Reviewers: ashoat, ginsu, rohan, tomek Reviewed By: ashoat Differential Revision: https://phab.comm.dev/D9907
- Loading branch information
1 parent
97e284e
commit 7c75580
Showing
70 changed files
with
406 additions
and
221 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.