I'm worried about a scenario where the user doesn't open the app for a couple of days, and when they do all ops are suddenly deleted before they can be processed. Are we protected against that somehow?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 2 2024
Aug 1 2024
In D12952#366364, @bartek wrote:As far as I have context, this makes sense!
NOTE: We should add a note on Releases and Beyond that we need to deploy prod Identity before releasing native/web
In D12914#366270, @tomek wrote:What about +community?: ?string, field?
I got a little confused here. But I think that communities are always thin because they live on keyservers. So for a thick thread, it is not possible to assign a community. Am I right?
Jul 31 2024
Capitalize
Yeah, I think that's the plan
Not sure if @ashoat's comment demands changes to this diff, please make sure to address it
This is great!
Can't we handle this in useProcessDMOperation just like canBeProcessed?
Should we set the unread status?
What about +community?: ?string, field?
Jul 30 2024
Jul 26 2024
Fix case
Change case
Rename
Add newline
Requesting review because I am not familiar with cpp and a lot of decisions had to be made
Use MessageType::SIDEBAR_SOURCE, update MessageType. Had to move MessageType to avoid importing folly on web
Jul 25 2024
In D12866#364118, @tomek wrote:Have you tested it on both platforms?
Rebase
Rebase
Address review
Address review
Jul 24 2024
One thing that doesnât work in thick threads is fetching next pages of results. This is because timestamps exceed cpp int, so SQLiteQueryExecutor::searchMessages doesnât bind them to sql query correctly. Fixing this is tracked in ENG-8893
Jul 23 2024
Rebase
Move code to db-ops-reducer.js
Rebase
wasm
wasm
wasm
Add CMake changes. Tested that android builds and no errors are thrown
Jul 22 2024
Make read-only