Skip to content
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

Merged
merged 47 commits into from
Oct 14, 2024

Conversation

ThomasSession
Copy link
Collaborator

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.

ThomasArtProcessors and others added 30 commits June 11, 2024 10:24
Also cleaned up older references to align with newer look
Cleaning unused code
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
@ThomasSession ThomasSession marked this pull request as ready for review October 9, 2024 04:53
Copy link
Collaborator

@AL-Session AL-Session left a 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.

}
}

override suspend fun delete1on1MessagesRemotely(
Copy link
Collaborator

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?

Copy link
Collaborator Author

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.
@ThomasSession ThomasSession merged commit 54ef260 into dev Oct 14, 2024
2 checks passed
@ThomasSession ThomasSession deleted the feature/standardised-message-deletion branch October 14, 2024 04:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants