Replace bare catch (_) in social and forum screens with reportSilently
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 75/100
Research direction
Read the six listed social and forum UI files and app/lib/core/utils/error_reporter.dart to check each catch and decide whether the failure is expected. Update the bare catches accordingly, then adjust _bareCatchBaseline in app/test/core/utils/error_reporter_test.dart. Done when the baseline reflects the remaining catches and flutter test passes.
Written by the indexing model from the issue text.
Description
A bare catch (_) {} swallows an error that never reaches Crashlytics, so bugs show up as "it just didn't work". The test app/test/core/utils/error_reporter_test.dart caps how many are left (_bareCatchBaseline = 54).
This issue covers the social and forum UI files with one bare catch each:
app/lib/features/social/presentation/screens/notifications_screen.dartapp/lib/features/social/presentation/screens/social_screen.dartapp/lib/features/social/presentation/widgets/group_ride_friend_picker.dartapp/lib/features/social/presentation/widgets/join_group_ride_by_code_sheet.dartapp/lib/features/social/presentation/widgets/shared_ride_feed_card.dartapp/lib/features/forums/presentation/screens/forum_thread_screen.dart
For each one
- If the failure is unexpected, change it to
catch (e, st)and callreportSilently(e, st, where: '...')fromapp/lib/core/utils/error_reporter.dart. Keep what the user sees the same. - If swallowing is expected (for example, "already deleted"), keep it and add a one-line comment saying why.
Done when _bareCatchBaseline is lowered to the new count and flutter test passes.
- Dominant language
- Dart
- Stars
- 4
- Forks
- 1
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 7
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 blankframe-tech/ThrottleIQ
-
dart enhancement help wanted translation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
blankframe-tech/ThrottleIQ#35 ·
Maintainers usually reply within 5 days
-
Review the machine-drafted Bangla strings (native speakers wanted)Possibly taken @RanaKhan77 claimed this 1 day ago. Opengood first issue help wanted translation
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
blankframe-tech/ThrottleIQ#23 · 6 comments ·
Maintainers usually reply within 5 days
-
dart enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 66/100
blankframe-tech/ThrottleIQ#51 ·
Maintainers usually reply within 5 days
-
dart enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 52/100
blankframe-tech/ThrottleIQ#48 ·
Maintainers usually reply within 5 days
-
dart enhancement help wanted translation
Difficulty 4/5 3-5 days Newbie friendliness 54/100
blankframe-tech/ThrottleIQ#43 ·
Maintainers usually reply within 5 days
All issues in blankframe-tech/ThrottleIQ
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Tencent/tdesign-flutter#1229 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
VeryGoodOpenSource/very_good_analysis#254 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
berkmancenter/frankly#732 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
rodydavis/signals.dart#510 ·