ProjectSidewalk/SidewalkGallery

Use descriptive text for severities

Open

#33 opened on Jun 12, 2020

View on GitHub
 (0 comments) (0 reactions) (1 assignee)TypeScript (0 forks)auto 404
backendgood first issue

Repository metrics

Stars
 (1 star)
PR merge metrics
 (PR metrics pending)

Description

Instead of displaying severity 1, 2, 3, 4, 5, use the actual words to describe problems.

We probably want to get this directly from the database, rather than just adding more constants to the frontend, since the constants file is already starting to get unwieldy.

Contributor guide

Research direction
Look at how severities are stored in the database and create a function to map numeric severities to descriptive text. Update the frontend to use this function instead of hardcoded constants.
Tech stack
typescript
Domain
full stack
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60