gbowne1/reactsocialnetwork

[feature]: Build an issue reporting system with a panel or modal

Open

#283 opened on Jul 7, 2023

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)JavaScript (60 forks)auto 404
designenhancementfeaturefrontendgood first issuehacktoberfesthelp wantedhigh-priority

Repository metrics

Stars
 (46 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe.

Needs a reporting system panel or modal something that might look like:

Screenshot 2023-07-07 at 15-07-40 (1) Luna Zhang _ Twitter

and

Screenshot 2023-07-07 at 15-20-15 (1) Luna Zhang _ Twitter

The problem with this particular one being is that:

  1. there is no selection of what type of issue is being reported
  2. Inability to report issues coming from multiple sources (users, etc.)

Describe the solution you would like

Some sort of panel or modal that allows reporting of any type of issue, whether it be spam, harmful, against TOS, etc. etc.

Describe the alternatives you have tried

Facebook, Nextdoor, GitHub and Twitter and a bunch of others have issue reporting systems but many of these have lots to be desired.

Additional context

No response

Contributor guide

Research direction
Review existing modal components in the repository (e.g., how other modals are structured), then create a new IssueReportModal component with a form for selecting issue type (spam, harmful, etc.) and a text area for description. Ensure it can be triggered from multiple locations (e.g., user profile, post).
Tech stack
javascriptreact
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitReactMUI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60