DEMO的页面push生硬
建议使用默认的 Navigator.pushName
这么生硬的DEMO很影响Flutter在开发者技术选型时的判断

看了fish-redux的todoList demo，发现里面连接全局状态的方法是使用visitor

visitor: (String path, Page<Object, dynamic> page) {
      /// 只有特定的范围的 Page 才需要建立和 AppStore 的连接关系
      /// 满足 Page<T> ，T 是 GlobalBaseState 的子类
      if (page.isTypeof<GlobalBaseState>()) {
        /// 建立 AppStore 驱动 PageStore 的单向数据连接
        /// 1. 参数1 AppStore
        /// 2. 参数2 当 AppStore.state 变化时, PageStore.state 该如何变化
     

Is your feature request related to a problem? Please describe.
Navigator 2.0 and Router have been released and are now the recommended approach:

Currently, there is no recipe for this, there are only recipes for a Navigator-less approach and for the old 1.0 imperative approach:

https://bloclibrary.dev/#/recipesflutternavigation

Describe the solution you'd like
Document a recipe

Web socket as data Provider

todos_repository_simple explains nicely about the benefits of using repository as singleton. But no where it's mentioned how to handle the web sockets.

How can I use web socket (webSocket and fileStorage) instead of rest (webClient and fileStorage) ?

Some key points between web socket and rest.

• The name itself signify socket

We want to use caching to speed up Appwrite's Travis CI build process, and we can use the community help here.

Currently our build process time is around ~10 minutes which is OK, but as faster it can be less time maintainers needs to wait for confirmation that there changes are running as expected.

This change should be focused on our Travis CI YAML file. Any suggestions for improving the co

I am able to send notifications with my Firebase Console to my iOS 6 14+ OS.
I have followed these steps https://firebase.flutter.dev/docs/messaging/apple-integration.

However, what is missing on this page is that notifications can be only received in the iOS when the app is killed. It does not work when the app is running (in fo