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

E/flutter (13373): [ERROR:flutter/lib/ui/ui_dart_state.cc(166)] Unhandled Exception: 'package:flutter/src/widgets/scroll_controller.dart': Failed assertion: line 112 pos 12: '_positions.isNotEmpty': ScrollController not attached to any scroll views.

class ArticlesList extends StatefulWidget {
  @override
  _ArticlesListState createState() => _ArticlesListState();
}

class _ArticlesL

From version 0.7 the Appwrite containers requires a reload for any changes to get applied. This is due to the fact that most of the codebase is loaded into memory for performance boosting.

We need help setting up a hot reload solution to our code when making changes during development.

From my short research this looks like a nice idea for a Docker based solution:
https://github.com/apogia

I'm attempting to implement the Initializing Flutterfire FutureBuilder approach with Flutter 1.20 and hitting the following exception:

$ flutter --version
Flutter 1.20.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 216dee60c0 (7 days ago) • 2020-09-01 12:24:47 -0700
Engine • revi