This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
apply plugin: 'maven-publish' | |
apply plugin: 'signing' | |
task androidSourcesJar(type: Jar) { | |
archiveClassifier.set('sources') | |
if (project.plugins.findPlugin("com.android.library")) { | |
from android.sourceSets.main.java.srcDirs | |
from android.sourceSets.main.kotlin.srcDirs | |
} else { | |
from sourceSets.main.java.srcDirs |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is real project screen with complex UI that was switched | |
from using the MVP with Moxy library | |
to the use of RxPM pattern (Reactive Presentation Model) with Outlast library (persistent PM layer). | |
I was doing it to see pros and cons of the RxPM pattern. | |
Pros: | |
- easy integration with RxBindings for complex UI. | |
- nice saved states in PM (for PM and MVVM lovers). | |
- easy combining of reactive streams coming from network, db, etc. in PM. |