-
Notifications
You must be signed in to change notification settings - Fork 6
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
fix: send HEIC images as normal files #2057
fix: send HEIC images as normal files #2057
Conversation
Shouldn't be fixed in this PR ? |
Datadog ReportAll test runs ✅ 2 Total Test Services: 0 Failed, 0 with New Flaky, 2 Passed Test Services
|
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 am uncertain if image resizing should be done by kalium, or even deciding if an image is inline of not.
Asking the real questions.
Perhaps we shouldn't decide on Kalium, really.
Kalium should probably just expose the "known" mime types in some categories. Perhaps in a sealed interface / enum or similar.
Apps should be the ones to decide whether something is "displayable" or not.
If the phone doesn't support heic
, then it should be displayed as a generic file, for example.
Arguably, the iOS app should convert the images to more streamlined formats, and Android apps sending this could just send as generic assets.
Co-authored-by: Mohamad Jaara <[email protected]>
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Issues
Solutions
I am uncertain if image resizing should be done by kalium, or even deciding if an image is inline of not.
for now removing heic from the list of inline images solve the issues but we should refactor this part and move the isDisplayableImageMimeType to consumer apps
Dependencies (Optional)
If there are some other pull requests related to this one (e.g. new releases of frameworks), specify them here.
Needs releases with:
Testing
Test Coverage (Optional)
How to Test
Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.
Notes (Optional)
Specify here any other facts that you think are important for this issue.
Attachments (Optional)
Attachments like images, videos, etc. (drag and drop in the text box)
PR Post Submission Checklist for internal contributors (Optional)
PR Post Merge Checklist for internal contributors
References
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.