Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Polish] Define an injectable connectivity stream

未关闭
#5 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
84/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
dart, flutter
领域
mobile

调研方向

Start with lib/screens/sign_in_screen.dart and inspect how the sign-in button and screen state are built; then review pubspec.yaml and the Flutter test setup. Add the monitor in lib/connectivity/connectivity_monitor.dart and cover its injected stream in test/offline_banner_test.dart. Done means offline shows the banner and disables Sign In, online removes both effects, and the Flutter checks pass.

由索引模型根据 Issue 内容生成。

描述

polish

What to build

Define the small connection-status interface that the app’s offline banner will use. Tests should be able to send online/offline changes without relying on the phone’s real network.

Files

  • lib/connectivity/connectivity_monitor.dart (new file)
  • Starting example: lib/app.dart
    Code to add or extend: abstract interface class ConnectivityMonitor { Stream<bool> get online; Future<void> dispose(); }.

Steps

  1. Add ConnectivityMonitor with Stream online and Future dispose(). true means the device has a network connection; it does not guarantee the internet is reachable.
  2. In tests, add FakeConnectivityMonitor using StreamController.broadcast(), an online getter and emit(bool). Close the controller in dispose.
  3. Check that emit(false) then emit(true) delivers those values. This issue defines the connection source; the next one adds the real library.

Example

emit(false),emit(true) produces those two events; disposing closes the stream.

Check it works

In test/connectivity/connectivity_monitor_5_test.dart, check the example above and the failure or limit described in the steps. Run flutter test test/connectivity/connectivity_monitor_5_test.dart and flutter analyze.

References

Assign yourself before starting, or comment to claim the issue. Project setup.

主要语言
PLpgSQL
星标
0
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DevDogsUGA/DogPack 的其他 Issue

查看 DevDogsUGA/DogPack 的全部 Issue

相似的 Issue

更多 Mobile Dev Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。