Skip to content

Feature/expired attachments #1037

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

Merged
merged 29 commits into from
Mar 27, 2025
Merged

Feature/expired attachments #1037

merged 29 commits into from
Mar 27, 2025

Conversation

ThomasSession
Copy link
Collaborator

SES-3518 - Changes to the attachment control.
View Jira ticket for details as a fair bit has changed visually including in the messages, control messages, quotes, message details screen.

Pending/Expired attachments now use different icons for different types
Consistent padding and styling for bubbled control messages (call cm, deleted message, pending/expired attachments)
…sibility now

Handling loading and failed state in attachment controls
Also added a new debug menu item to "untrust" attachments
ViewVisibleMessageContentBinding.inflate(LayoutInflater.from(it)).mainContainerConstraint.apply {
factory = { context ->
// Inflate the view once
ViewVisibleMessageContentBinding.inflate(LayoutInflater.from(context)).mainContainerConstraint
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although it's existing code I think it's better to use the rootView instead of a specific view so you don't accidentally move that view off the root:

Suggested change
ViewVisibleMessageContentBinding.inflate(LayoutInflater.from(context)).mainContainerConstraint
ViewVisibleMessageContentBinding.inflate(LayoutInflater.from(context)).root

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed

Comment on lines 90 to 92
(context.contentResolver.observeChanges(DatabaseContentProviders.Conversation.getUriForThread(messageRecord.threadId)) as Flow<*>)
.onStart { emit(Unit) }
.collect{
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we have changed the flow source, do you think we should add in some debounces?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a debounce

@ThomasSession ThomasSession merged commit b20b02b into dev Mar 27, 2025
4 checks passed
@SessionHero01 SessionHero01 mentioned this pull request Apr 29, 2025
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.

2 participants