-
Notifications
You must be signed in to change notification settings - Fork 3
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
Loading screen #89
Loading screen #89
Conversation
Code("code", R.drawable.il_code); | ||
|
||
companion object { | ||
fun findIllustrationByCategory(category: String) = |
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.
this fun returns TechCategory not illustration. I think "from" will be enough for this method name.
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.
You mean findIllustrationFrom(category: String)
? @kdiakonidze
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.
no, just "from" .from(category: String)
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.
hmm do not know, do not like just from
does not gives information what it does
maybe just findSpecific()
?
@kdiakonidze @shalva97
what do you think guys?
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.
it returns the class from which it was called, our case TechCategory.
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.
Yep and i think findSpecific()
will be informational name for that kind of function
Loading screen before tests are loaded