[Report & Block] Replace unavailable/quarantined session detail
还没有人认领这个 Issue。
评估
调研方向
Start in lib/screens/sessions/session_detail_screen.dart, which this issue extends from #118, and look at how loadSession's null result and permission or moderation refusals are handled before the screen builds. The starting example is lib/screens/retry_screen.dart, which shows the Refresh and Back pattern. Done means a previously visible meeting that becomes unavailable shows only the unavailable message, passes test/screens/sessions/session_detail_screen_dp_r07_test.dart, and leaves flutter analyze clean. Wait for #118 to land before starting.
由索引模型根据 Issue 内容生成。
描述
What to build
Replace meeting details when a previously visible meeting becomes unavailable. Clear the old title, host and location so blocked or hidden content cannot remain on screen from an earlier load.
Files
lib/screens/sessions/session_detail_screen.dart(extend the prerequisite’s file)- Starting example: lib/screens/retry_screen.dart
Steps
- When loadSession returns null or a permission/hidden-content refusal, clear the stored meeting before building the screen.
- Show “This session is unavailable.” with Refresh and Back actions. Do not keep its old title, host or location visible.
- Give the same unavailable message whether the meeting is missing, blocked or hidden by moderation. Test a previously visible meeting that becomes unavailable.
Example
Previously visible test example becomes hidden → old content no longer rendered.
Check it works
In test/screens/sessions/session_detail_screen_dp_r07_test.dart, check the example above and the failure or limit described in the steps. Run flutter test test/screens/sessions/session_detail_screen_dp_r07_test.dart and flutter analyze.
Before starting
- #118 — Confirm block and invalidate visibility
References
Assign yourself before starting, or comment to claim the issue. Project setup.
- 主要语言
- PLpgSQL
- 星标
- 0
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
DevDogsUGA/DogPack 的其他 Issue
-
polish
难度 2/5 1-3 小时 新手友好度 72/100
DevDogsUGA/DogPack#131 ·
-
polish
难度 2/5 1-3 小时 新手友好度 65/100
DevDogsUGA/DogPack#130 ·
-
moderation
难度 2/5 1-3 小时 新手友好度 75/100
DevDogsUGA/DogPack#119 ·
-
moderation
难度 2/5 1-3 小时 新手友好度 85/100
DevDogsUGA/DogPack#113 ·
-
discover
难度 2/5 1-3 小时 新手友好度 74/100
DevDogsUGA/DogPack#106 ·
查看 DevDogsUGA/DogPack 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
nightscout/nightguard#368 ·
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
react-native-maps/react-native-maps#6031 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 62/100
-
难度 2/5 1-3 小时 新手友好度 78/100
bisq-network/bisq-mobile#1948 ·
维护者通常 1 天内回复