rebase and land
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Thu, Apr 18
rebase and land
In D11624#334284, @tomek wrote:Do we need a dedicated validator for UpdateRelationshipMessage?
land
land
rebase and aldn
Wed, Apr 17
address feedback and land
rebase BEFORE addressing feedback
This is safe to land since we don't have equivalent to https://github.com/CommE2E/comm/commit/7024301fcda748efefa900bd952cd8e127aac87d landed on master yet so these messages aren't currently getting created.
address @tomek's feedback
JK, we need D11606 to land this
rebase and land
This diff is safe to land since we're just narrowing flow types on the clients. No runtime changes so this shouldn't break anything.
rebase and land
This diff is safe to land as is as it broadens what arguments createPersonalThreads can accept and TraditionalRelationshipRequests will continue to work as expected.
Looks good
Tue, Apr 16
remove hack from stack
fix TUnion import
Mon, Apr 15
Looks good, let's definitely memoize return value of TagFarcasterChannelNavigator.
Code changes look good, would be good to make sure all other notes left by other reviewers are addressed/responded to before landing.
Fri, Apr 12
Thu, Apr 11
Looks good. (There shouldn't be any WASM stuff that needs to be generated for the non-DB code here right?)
Would also be good to include some screenshots of what it looks like in Test Plan so reviewers can side-by-side with the Figma designs
Wed, Apr 10
rebase
rebasing
rebasing
address @tomek's feedback
rebasing stack
address @ashoat's feedback
address @tomek's feedback
land
land
As discussed offline it might make sense to do something like
land
jk, you already handled this in stack
Might be missing something, but don't we also need to update default states? For example in defaultWebState?