[Discover + Join/Leave] Map enrollment/host/onboarding join errors
还没有人认领这个 Issue。
评估
调研方向
Start in lib/sessions/join_errors.dart, which #106 must create or extend first, and look at joinErrorMessage and the new recoveryFor(String reason); the enrollment reference is supabase/schemas/dogpack/tables/session_members.sql. Add the JoinRecovery enum and the not_enrolled, host_cannot_join and onboarding_required mappings with their messages, then have the consumer recheck the account only for onboarding. Done when flutter test test/sessions/join_errors_dp_d04_3_test.dart and flutter analyze pass.
由索引模型根据 Issue 内容生成。
描述
What to build
Explain the remaining join refusals and offer the correct next action. A missing course, a host trying to join their own meeting and incomplete setup need different recovery behavior.
Files
lib/sessions/join_errors.dart(extend the prerequisite’s file)- Starting example: supabase/schemas/dogpack/tables/session_members.sql
Code to add or extend:JoinRecovery recoveryFor(String reason).
Steps
- Declare enum recovery none/profile/manage/onboarding/refresh. Map not_enrolled→profile,host_cannot_join→manage,onboarding_required→onboarding, the earlier full/closed/unavailable→refresh.
- In
joinErrorMessage, use “Add this course to your profile before joining.” fornot_enrolled, “You host this session; use Manage instead.” forhost_cannot_join, and “Finish setup before joining.” foronboarding_required. - Consumer calls account recheck only for onboarding, rather than any PT403.
Example
not_enrolled offers profile; host_cannot_join offers Manage; onboarding_required re-enters account check.
Check it works
In test/sessions/join_errors_dp_d04_3_test.dart, check the example above and the failure or limit described in the steps. Run flutter test test/sessions/join_errors_dp_d04_3_test.dart and flutter analyze.
Before starting
- #106 — Map session full/closed/unavailable join errors
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 小时 新手友好度 78/100
bisq-network/bisq-mobile#1948 ·
维护者通常 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 天内回复
-
Enhancement
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
GantMan/jail-monkey#380 ·