[Report & Block] Open session/profile reporting actions
还没有人认领这个 Issue。
评估
调研方向
Start from the existing report/block pattern in lib/screens/home_screen.dart, then extend lib/screens/sessions/session_detail_screen.dart and lib/screens/member_profile_screen.dart so the session menu reports session.id but blocks session.hostId, while the profile menu uses profile.userId for both. Verify with flutter test test/screens/sessions/session_detail_screen_dp_r05_test.dart and flutter analyze; the prerequisite issues #114-#116 should land first.
由索引模型根据 Issue 内容生成。
描述
What to build
Open reporting and blocking from the meeting/profile menus with the correct target. Reporting a meeting uses the meeting ID; blocking its host uses the host’s user ID.
Files
lib/screens/sessions/session_detail_screen.dart(extend the prerequisite’s file)lib/screens/member_profile_screen.dart(extend the prerequisite’s file)- Starting example: lib/screens/home_screen.dart
Steps
- For session menu pass contentType session/contentRef
session.id; for profile pass profile/contentRefprofile.userId. - Open ReportForm via modal with those exact inputs; hide/refuse self-report.
- Block target is
session.hostIdorprofile.userId, notsession.id; confirmations use existing callback.
Example
Reporting session42 does not report its host profile;blocking uses host UUID.
Check it works
In test/screens/sessions/session_detail_screen_dp_r05_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_test.dart and flutter analyze.
Before starting
- #114 — Bind report form submission outcomes
- #115 — Delete a caller-owned block
- #116 — Render authorized host profile detail
- #110 — Bind leave and refresh seats
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
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
bisq-network/bisq-mobile#1948 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
streetcomplete/StreetComplete#7286 · 2 条评论 ·
维护者通常 1 天内回复
-
bug-pending-triage
难度 2/5 1-3 小时 新手友好度 70/100
NativeScript/NativeScript#11525 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
callstack/agent-device#3627 ·
维护者通常 1 天内回复