Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Report & Block] Render report reason and description fields

Open Beginner friendly
#113 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
dart, flutter
Domain
frontend

Research direction

Create lib/widgets/report_form.dart, keeping the stored reason strings aligned with the agreed list in supabase/functions/_shared/moderation/messages.ts. Read docs/guides/testing.md and the Flutter widget-test cookbook before writing test/widgets/report_form_dp_r02_test.dart; the form takes an onSubmit callback and validates the explanation. Done means the eight reasons render with readable labels, the Other/blank, Spam/blank and 1001-character cases behave as described, and flutter test test/widgets/report_form_dp_r02_test.dart plus flutter analyze pass.

Written by the indexing model from the issue text.

Description

moderation

What to build

Build the report form using the eight agreed reasons and an optional explanation. Require an explanation for “Other” and enforce the maximum length before sending anything.

Files

Steps

  1. Offer harassment, hate_speech, spam, sexual_content, violence, impersonation, off_topic and other, with readable dropdown labels. Keep the stored reason strings unchanged.
  2. Add the explanation field. For other, require nonblank text after trimming; every explanation must be at most 1000 characters.
  3. Pass the checked reason/explanation to onSubmit. Check Other with blank text, Spam without text and an explanation of 1001 characters.

Example

Other+blank blocks;Spam+blank valid;1001 characters blocks.

Check it works

In test/widgets/report_form_dp_r02_test.dart, check the example above and the failure or limit described in the steps. Run flutter test test/widgets/report_form_dp_r02_test.dart and flutter analyze.

Before starting

  • #112 — Map report response/error outcomes

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DevDogsUGA/DogPack

All issues in DevDogsUGA/DogPack

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.