-
Notifications
You must be signed in to change notification settings - Fork 275
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
Base & mobile modules revision #76
Base & mobile modules revision #76
Conversation
Simplified logic. Fixed dereference of 'channel' may produce 'java.lang.NullPointerException'.
Removed unneded try
Moved to a public static variable
A question, Who is the API owner? |
Guess I am, I developed it. |
The common per quality torrent includes If we are the API owners the reponse and entity treatmen for each provider could be simplified a lot, we should not need I can contribute with the API backend to do some improvements if you need some help, I am not a good frontend developer, but I am very experienced with backend development. |
At the time of developing the API I didn't touch the android or desktop version, so in order to keep those working I ended up using the old value names. Now I'm fine with changing it for consistency reasons. |
Thank you, Chris, first step should be change the |
Two files would need to be changed: And the current field names in the MongoDB database would need to be updated. |
Great!! tell me when we are in production to modify both, desktop and Android applications. API mod PR ready |
This PR fixes #65 too, and probably others... |
Member variables to local. Removed deprecated methods.
To solve the load of not initialized fragments on change genre we always load the results because does not affect performance and ensure that the movies with that genre are loaded into the MediaListFragment when we clicked on the navigation item
I announce that we have an Android mobile version almost usable 😊 |
LeakCanary.install(this); | ||
Foreground.init(this); | ||
|
||
//initialise logging | ||
if (BuildConfig.DEBUG) { | ||
if (debugable || BuildConfig.DEBUG) { |
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.
not totally sure, but the debuggable flag manages BuildConfig.DEBUG
so this would be double checking the same thing
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 that BuildConfig.DEBUG
has no effect at Android Studio debugging runtime.
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.
According to this BuildConfig.DEBUG
should be enough
I was halfway when I decided that I'm not even going to look at it all. If it works, then 👍 wow. Some refactoring was really needed |
btw, i saw that butter moved forward with using dagger. maybe there is some way to merge it somewhere? not really easy i guess |
This is impossible to merge, I am afraid of we have to do it manually, dagger and OkHttp 3. |
Butterknife update
Picasso improvements
New response treatment for providers API (with jackson, removed slow GSON)
Other Java language fixes.