Accepting assuming landing without console logs
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Sep 25 2024
Sep 24 2024
Sep 23 2024
Sep 22 2024
Sep 20 2024
Sep 18 2024
Sep 17 2024
Sep 16 2024
In D13350#376127, @ashoat wrote:Seems like some copy-paste here that could be factored out
final rebase
remove unnecesssary Thick thread type import
rebase
keep op time field consistent in edit entry operation. rename lastUpdatedTo field to time
update useDeleteEntry to await sending DM op
review feedback
review feedback
review feedback
rebase
Abandoning. Following discussion in https://linear.app/comm/issue/ENG-8745/create-dmoperations-for-restoreentrymessageinfo#comment-8eb5b44d, this is no longer necessary
update lastUpdatedTime in delete entry op to be time
Requesting review. Timestamp check included in future diff and will prioritize landing this by organizing code in a future diff
Rerequesting review
In D13340#375962, @tomek wrote:It is a bit confusing to see all this info being sent while deleting an entry. It might be invalid when one user edits an entry while someone else deletes it.
The proper solution would require:
- Modifying the payload to contain just the ID of the deleted entry without too many details
- Introducing a util that provides all the entry infos
- Introducing a separate timestamp for deleted property
This will take some time, and we're short on it, so we should search for a simpler solution.
What we can do for now, is to keep the current approach and introduce a lastUpdatedTime timestamp check.