rebase
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Sep 18 2023
address feedback: early-return
rebase
rebase
rebase after resolve merge conflict
Memoize boundCallServerEndpointSelector per keserverID
In D9211#271261, @tomek wrote:Have you tested if memoizing the list is beneficial? FlatList is already memoized internally (PureComponent) so wrapping it with memo shouldn't improve anything, but maybe I'm missing something.
Set auto cancel property to false only for staff releases
Don't forget to create one for the input validator idea too!
Fix flow
Fix flow bugs
Rebuild
Rebuild
I created a followup task to update the types: ENG-4968
Failing CI fix
There's code that exists for the search experience that handles finding a thread for a given user if it already exists, OR creating a "pending" thread if that thread doesn't exist yet.
How does the code for search results currently handle this?
Looks good, but would be great if @tomek could take a look, as he's more familiar with our Android notif code
Refactor using isStaffRelease utility.
Have you tested if memoizing the list is beneficial? FlatList is already memoized internally (PureComponent) so wrapping it with memo shouldn't improve anything, but maybe I'm missing something.
Unfortunate that we can't use ReturnType<T> and Parameters<T> from new versions of flow, might simplify it a little
Use new syntax
Destructure options.
Requesting changes to fix failing CI - most likely wrong uuid version is being resolved, try the yarn why uuid command to confirm.
Sep 17 2023
type fn return values as mixed
rebase and land
rebase and land
rebase and land
Sep 16 2023
Nice thank you!!
Sep 15 2023
In D9215#271132, @rohan wrote:Accepting since it seems reasonable to me, but not super familiar with why we introduced it here in the first place so letting others take a look
In D9214#271139, @rohan wrote:If the performance isn't impacted much one way or the other, is the memory usage of memoizing this not noticeable as well?
Nice to see the code a lot simpler!
If the performance isn't impacted much one way or the other, is the memory usage of memoizing this not noticeable as well?
Accepting since it seems reasonable to me, but not super familiar with why we introduced it here in the first place so letting others take a look
Did you test whether the animation still works when user opens tooltip and presses "thread", even if the message has a link?
Rebase before landing
Rebase before landing
Return instead of modifying
Fixes