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

🚀 Feature

(A clear and concise description of what the feature is.)

Have you spent some time to check if this issue has been raised before?

(Have you googled for a similar issue or checked our older issues for a similar bug)
Yes

Have you read the Code of Conduct?

Yes

Pitch

A common way to mana

New Issue Checklist

• [X ] I have searched for a similar issue in the project and found none

Issue Info

Returning to Flutter dev after a hiatus and I'm trying to write a widget test for a widget that uses a cubit. For this I use a mock generated with mockito (for nullsafety) and try to stub it using whenListen from bloc_test 8.1.x, and it fails (e.g. it says that .state stubbing is missing). I took a peek into the implementation of this function and it uses mocktail internally.

Question: I

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

https://firebase.flutter.dev/docs/cli/#usage

1. the question marks are 404s when you click on them - under the crashlytics tab
   2a. the first grey box i receive the overall impression 'maybe skip dart only initialization for everything in this table'
   2b. the second grey box i receive the overall impression 'maybe it'll be fine, you'll just see some warnings'.

i appreciate the effort at spec

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,