-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/standardised message deletion #1685
Conversation
Also cleaned up older references to align with newer look
Cleaning unused code
…from the db directly
Split the `BASE_DELETED_TYPE` into two types: BASE_DELETED_OUTGOING_TYPE and BASE_DELETED_INCOMING_TYPE so we can differentiate them visually.
Still need to finalise "note to self" and "legacy groups"
Moving away from promises
Hndling unsend request retrieval as per figma docs
Sharing admin logic
Also rethemed the send buttona dn home plus button to have better ax contrast by standardising the colour displayed on the accent color to be the same as the one on the sent messages
We removed the 'delete locally' dialog, instead we show the 'delete for everyone' with the second option disabled
Cleaned up invisible copy button on black bgs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! A couple of minor suggestions for you to address as you see fit.
Will hold off on final approval until the TODO work is addressed & we can give it a final look through.
app/src/main/java/org/thoughtcrime/securesms/attachments/DatabaseAttachmentProvider.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/org/thoughtcrime/securesms/conversation/v2/ConversationActivityV2.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/org/thoughtcrime/securesms/conversation/v2/ConversationViewModel.kt
Show resolved
Hide resolved
app/src/main/java/org/thoughtcrime/securesms/conversation/v2/ConversationViewModel.kt
Show resolved
Hide resolved
app/src/main/java/org/thoughtcrime/securesms/conversation/v2/ConversationViewModel.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/org/thoughtcrime/securesms/repository/ConversationRepository.kt
Show resolved
Hide resolved
app/src/main/java/org/thoughtcrime/securesms/repository/ConversationRepository.kt
Outdated
Show resolved
Hide resolved
} | ||
} | ||
|
||
override suspend fun delete1on1MessagesRemotely( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see anything that requires suspend
in the function body?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made it a suspend as a safety mechanism to force the calling point to use this from a coroutine.
I guess another option would be to use a context directly in the method here to keep the responsibility local.
Only force the priority to visible when going from not approved to approved
Syncing happens in the bg so the user doesn't need to know of it hence the status can display as "Sent" during the syncing phase. Resyncing, in case it happens, can display the "Syncing" status as it would happen after a syncing error.
Jira ticket: [SES 1792]
Description:
Standardising message deletion across platforms.
See the Figma link in the Jira ticket for implementation details and updated UI and logic rules.