-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Glide - comments #8038
Glide - comments #8038
Changes from 9 commits
4d959d5
c08efde
2077af6
eb309fc
099f74b
f814cc1
6c80b7b
fc53936
d70e029
98678ee
9d289a2
d082585
6df0d32
26ddac0
e94aefd
fea9639
ba594f2
be33714
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,5 +5,6 @@ enum class ImageType { | |
VIDEO, | ||
AVATAR, | ||
BLAVATAR, | ||
THEME | ||
THEME, | ||
UNKNOWN_DIMENSIONS | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should just say There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 👍 I renamed it from UNKNOWN -> UNKNOWN_DIMENSION and I wasn't sure whether it was a good call or not. You made this decision easier -> I've renamed it back to UNKNOWN. |
||
} |
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.
Just curious, is it at all possible to avoid this many different
load
methods inImageManager
? Can we use a builder pattern or named parameters with default values to avoid it? This, of course, doesn't need to be part of this PR, but just a general concern.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've consider it before starting this project, however I felt it'd be nice to have limited options how to load images, so we can easily be consistent across the app. I also didn't want to have any Glide classes in the interface, but it could be solved by wrapping GlideRequest, I guess. However, I don't have a strong opinion on this. Wdyt?
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 think some kind of refactor would be great for this. I have to look into it more to figure out what the best way might be, but I think we simply have too many load functions right now.
As I said, this is not related to this PR, but something to consider before we finalize the Glide project.
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'd appreciate any help with it. We might allocate 30 minutes and resolve it during a call. Wdys?
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.
Sure thing. Do you want to open an issue for this and assign it to both of us, so we can check it out once all Glide PRs are merged in?