[Report & Block] Confirm block and invalidate visibility
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- dart, flutter, supabase
- 领域
- authorization, mobile
调研方向
Start in lib/screens/sessions/session_detail_screen.dart, which the prerequisite #117 reporting actions are expected to extend, and in lib/screens/home_screen.dart for the Discover and My sessions refresh. Confirm #117 is merged first, since the block action depends on it. Done means a confirmed block clears the blocked host's detail and refreshes both lists, a failed block keeps the existing content and shows an error, and test/screens/sessions/session_detail_screen_dp_r05_2_test.dart passes with flutter test and flutter analyze.
由索引模型根据 Issue 内容生成。
描述
What to build
Ask for confirmation before blocking a person, then refresh affected screens. Previously visible content should disappear when the server’s updated permissions make it unavailable.
Files
lib/screens/sessions/session_detail_screen.dart(extend the prerequisite’s file)- Starting example: lib/screens/home_screen.dart
Steps
- Show confirmation for selected target; await blockUser using caller/targetUUID.
- On success clear matching profile/session detail and refresh Discover/My sessions so server visibility decides.
- Failure retains previous content/error; no notification to blocked person.
Example
Blocked host’s open detail disappears after success; failed block leaves data visible.
Check it works
In test/screens/sessions/session_detail_screen_dp_r05_2_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_r05_2_test.dart and flutter analyze.
Before starting
- #117 — Open session/profile reporting actions
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
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
jbacalso24/mimry#291 ·
维护者通常 1 天内回复
-
ci-cd from-review-extraction python security severity:suggested
难度 2/5 1-3 小时 新手友好度 72/100
LearningCircuit/local-deep-research#7454 ·
维护者通常 2 天内回复
-
Change oauth client name?可能已有人在做 @nealrichardson 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 66/100
posit-dev/rsconnect-python#870 ·
维护者通常 1 天内回复
-
feedback
难度 2/5 1-3 小时 新手友好度 62/100
useagenthq/useagent#153 ·
维护者通常 2 天内回复
-
enhancement frontend good first issue
难度 2/5 1-3 小时 新手友好度 72/100
anujsharma8d/mockspire#7 · 1 条评论 ·