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 该如何变化
     

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

Is your feature request related to a problem? Please describe.
Currently, migrating from another library requires you to do a manual comparison of samples from both libraries to fill in the gaps. It would be nice to have documentation for people migrating from other popular state management solutions, such as ChangeNotifier, StateNotifier, MobX, or Redux.

Describe the solution you'd like

We need to design a single Docker container that can run all of the Appwrite services and internal processes using Supervisord. This should be a feature with Appwrite minimum, must-have features (ClamAV disabled, no need for Traefik). This is something we need to allow developers to run Appwrite easily on low-end systems and 1-click deployment services (Raspberry PI, Free hosting tiers, Heroku, Ki

I've finished up migrating a number of Firebase libraries from their old versions to the new ones. My main focus on the migration guide page was making sure I addressed all the BREAKING issues.

When testing the application, I've noticed a breaking change that is not reported in the documentation: the error codes for Firebase Auth have changed. I di