Requesting changes for some explanations so I can understand the diff better. Feel free to re-request.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 29 2024
Jan 25 2024
I think the diff description stopped matching the changes.
Improve logging
Jan 18 2024
Some renames and code refactor to make it cleaner
Some renames and code refactor to make it cleaner
Some renames and code refactor to make it cleaner
Jan 17 2024
Jan 16 2024
unwrap -> expect. Refactored the code into separate functions so it's cleaner.
Rebase
Fixes
Jan 15 2024
Rebase
Jan 12 2024
Jan 11 2024
When we open a new tab with the new version, old tabs are in the background so it should be safe because the worker should not be performing anything on DB.
Jan 10 2024
Jan 9 2024
Jan 8 2024
Removed a bit of code duplication for parsing ws messages
Fix rebase error
Remove Arcs
Respond to review
Removed logging of sensitive data.
Does your updated code already separate out only the threads from the newly logged-in keyserver for hashing?
Jan 5 2024
So this app state without keyservers will be visible to the users right? Do other features work or at least they don't crash the app? E.g. "Create new chat" and "create community" buttons, thread search, calendar view?
Jan 4 2024
Jan 3 2024
Jan 2 2024
In the future we might consider refactoring parse_{some_business_logic_name}_attribute() too, but it's not a direct purpose of this task, so I replaced only these "universal" functions
If I understand the error type correctly, shouldn't we use Value::String in places where we directly create Some(AttributeValue::S(...)?
Dec 22 2023
- Could we apply all transforms in persistConfig.transforms dynamically instead of "hardcoding" them in migrateStorageToSQLite?