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.
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: