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

Introduction

Appwrite has been and always will be a tool for developers. To emphasize this, we want to create the best developer experience possible by providing enough guides and examples for new Appwriters.

Your task is to write a blog post Ruby in Appwrite. The main topic of your article should be explaining how to use Appwrites Ruby SDK to write Appwrite Functions. It can be

It would be great to see, how to properly implement refreshing + pagination + search.

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

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

In the FlutterFire documentation is this

https://firebase.flutter.dev/docs/crashlytics/overview/#b-ios

But in official Firebase documentation is this:

![firebase_doc](https://user-images.githubusercontent.com/10598983/147497968-aa27c9ae-4c7e-44c4-b0e0-d567752ee9

What could be improved

Based on this issue: flame-engine/flame#954, I noticed that we could also go for the same approach for the packages' unit/widget tests execution,