feat(account): add support for PNG avatars #10505
Closed
+87
−28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR updates the account avatar logic to support both
.jpgand.pngfile extensions. Previously, all avatars were forced to use the.jpgextension, which caused issues when someone uploaded PNGs, especially those with transparency (I tried some for my main email and did not understand why it failed at first, or rather did not show the images in the picker).Changes:
Dynamic extension:
LocalAvatarImageDataSourcenow detects if the source image is a PNG and saves it with the correct.pngextension.delete()function now checks for and removes both.jpgand.pngfiles for the given account. This ensures that, when a user switches from a JPEG avatar to a PNG avatar (or vice versa), the old file is deleted and does not remain orphaned.LocalAvatarImageDataSourceTestto verify PNG support and ensure the clean-up logic works for multiple file types.Fixes:
#10501