[Discover + Join/Leave] Map session full/closed/unavailable join errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
Research direction
Start with the schema in supabase/schemas/dogpack/tables/session_members.sql to confirm the error codes session_full, session_closed and session_unavailable. Create lib/sessions/join_errors.dart with joinErrorMessage(String reason), mapping each code to its exact sentence and returning the generic 'Couldn't join. Refresh and try again.' for anything else. Done when test/sessions/join_errors_dp_d04_2_test.dart passes under flutter test and flutter analyze is clean.
Written by the indexing model from the issue text.
Description
What to build
Explain when joining fails because a meeting is full, closed or unavailable. Refresh its details rather than showing a successful join that did not happen.
Files
lib/sessions/join_errors.dart(new file)- Starting example: supabase/schemas/dogpack/tables/session_members.sql
Code to add or extend:String joinErrorMessage(String reason) first error family.
Steps
- Map session_full→This session is full.; session_closed→This session is closed.; session_unavailable→This session is unavailable.
- Unknown reason → Couldn’t join. Refresh and try again.
- UI requests a refresh after those three results; never expose the raw DB object.
Example
Each stable server error code has an exact sentence; unknown remains generic.
Check it works
In test/sessions/join_errors_dp_d04_2_test.dart, check the example above and the failure or limit described in the steps. Run flutter test test/sessions/join_errors_dp_d04_2_test.dart and flutter analyze.
Before starting
- #31 — Join with a plain own-membership insert
References
Assign yourself before starting, or comment to claim the issue. Project setup.
- Dominant language
- PLpgSQL
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DevDogsUGA/DogPack
-
polish
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DevDogsUGA/DogPack#131 ·
-
polish
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
DevDogsUGA/DogPack#130 ·
-
moderation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
DevDogsUGA/DogPack#119 ·
-
moderation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
DevDogsUGA/DogPack#113 ·
-
discover
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
DevDogsUGA/DogPack#99 ·
All issues in DevDogsUGA/DogPack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
callstack/agent-device#3627 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GantMan/jail-monkey#380 ·
-
backlog:low bug localization
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
simonoppowa/OpenNutriTracker#1366 ·
Maintainers usually reply within 1 day
-
area: android bug good first issue P3 testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Nileshsri2022/chat-puter-vision#54 ·
Maintainers usually reply within 1 day
-
MDM: interfaceName cannot be set through managed configurationsPossibly taken @JulienUsson claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 82/100
bk138/droidVNC-NG#404 · 1 comment ·