Closed kean closed 4 days ago
App Name | WordPress Alpha | |
Configuration | Release-Alpha | |
Build Number | pr23832-c2aeec8 | |
Version | 25.4.2 | |
Bundle ID | org.wordpress.alpha | |
Commit | c2aeec8ce39395717b46145d9a4d917887010b4e | |
App Center Build | WPiOS - One-Offs #11080 |
App Name | Jetpack Alpha | |
Configuration | Release-Alpha | |
Build Number | pr23832-c2aeec8 | |
Version | 25.4.2 | |
Bundle ID | com.jetpack.alpha | |
Commit | c2aeec8ce39395717b46145d9a4d917887010b4e | |
App Center Build | jetpack-installable-builds #10121 |
I'm working towards removing
AlamofireImage
. The previousdownloadSiteIcon
variants and uses have been completely replaced withSiteIconView
,SiteIconViewModel
, andImageDownloader
in all other places. This was the only remaining use case, but I'm not entirely sure why it's usingdownloadSiteIcon
. My understanding is that it's a fallback for loading non-gravatar user avatars if that's still a thing. I think it's going to be safe to just load the image from the URL as is in this case.To test:
I tested it by commenting out
if let gravatar = AvatarURL(url: url) {
line and letting the new code run.Regression Notes
Potential unintended areas of impact
What I did to test those areas of impact (or what existing automated tests I relied on)
What automated tests I added (or what prevented me from doing so)
PR submission checklist:
RELEASE-NOTES.txt
if necessary.Testing checklist: