Some class from sample app should be in the library about mavericks HOT 2 CLOSED

@eboudrant @elihart There was a reason for each one:

• MvRxViewModel: it requires you to pass debugMode into super. You should use the BuildConfig constant from your application package which we can't do for you.
• BaseMvRxFragment. You should also have a BaseFragment in your app in which you can put shared code. We recommend having your app's BaseFragment extend BaseMvRxFragment and do not recommend using BaseMvRxFragment directly.

I get that this is slightly confusing so I added a few sentences to this wiki page explaining this.

from mavericks.

I think it's reasonable to provide some of this in a module that we ship.

The downside is that so much of the fragment implementation is up to how you choose to use MvRx, so it's hard to provide a one size fits all solution.

Playing devil's advocate, how hard is it to copy 1 or 2 files? We could update the documentation to be more clear about where the files live.

from mavericks.