Since a good architecture serves to make it easy to swap implementations I think it would be nice to have one or more samples which demonstrate how a data source implementation using a combination of a remote api, and a local sqlite database can be replaced with a realtime database.

I am not sure yet how it would be possible to run the same espresso tests in such a sample since mocking the fire

Could someone explain me why Navigator's methods are calling from activity, not from fragment directly? Why first we invoke presenter's method which in turn invoke fragment's method which invoke activity's method?

Look at here

• → Did you conform to the Rules?
• → Did you read the Wiki Carefully?
• → Did you search in Google?
• → Did you search in openned&closed Issues?
• → Receive only bugs and suggestions

Environment

• MVPArms Version:
• Android

Hi all friends
Friends, to better understand this framework, let's do everything by example
Examples help us to master this framework more effectively
Examples can be as follows, such as forms, lists, and even small projects. This can help a great deal.
Form Submit

Lists

为了让 Component 更好, 我设计了这个奖励机制. 凡是满足以下的条件的 bug 都会奖励 25 元的奶茶钱. 钱虽然不多, 重在感谢

Bug 满足条件

• 必须是能复现的
• 必须是 Component 项目中的bug, 不能是其他第三方库的, Idea Plugin 不算在其中. 因为插件属于帮助性的工具, 出问题也不影响你们开发
• 必须是没有其他人反馈过的 Bug
• 必须是我认可的：首先如果真的是 bug, 我不会为了这点钱死皮赖脸不承认. 因为之前看下来, 很多 bug 都是用户自己配置有问题或者代码写的不对引起的, 并不是框架的问题. 所以这个是需要我来判断的. 当然了, 你足够了解 Component 的话, 你自己也会知道到底是不是 Component 的问题

所有发现 bug 受奖励的名单, 会持续更新(

Description

I wanted to request that you migrate your code from Fabric to Firebase.

Basic Information

• Device type: Android
• OS version:
• App version:

In MVI core demo app you pass AndroidTimeCapsule in Feature2 through constructor.

class Feature2(
    timeCapsule: TimeCapsule<Parcelable>? = null
) : ActorReducerFeature<Wish, Effect, State, News>(
...

How it supposed to be used with Android lifecycle methods onRestoreInstanceState and onSaveInstanceState?