CodeForPhilly / CodeForPhilly/codeforphilly-ng
RelativeTime component for the 13 <time dateTime title> sites
- Langage dominant
- TypeScript
- Étoiles
- 1
- Forks
- 1
- Merge moyen
- 5 j 3 h
- PR mergées (30 j)
- 9
Description
## Context
PR #157 converted every relative or `title`-only date in `apps/web` to `` — 13 sites after the sweep, across `ActivityCard`, `HelpWantedCard`, `BlogIndex`, `BlogDetail`, `Account`, `AccountClaim`, `StaffAccountClaimQueue`, `PersonDetail`, `ProjectDetail`.
## Problem
Three attributes and two formatter calls per site, all identical. The next date rendered in the app will likely drop one of them (that is exactly how three sites were missed on the first pass of #157).
## Proposal
A `RelativeTime` component (`apps/web/src/components/RelativeTime.tsx`) taking `iso` and an optional `className`, rendering the `
Deferred from `plans/a11y-mechanical.md` (PR #157).
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Start with apps/web/src/components/RelativeTime.tsx and review PR #157 plus plans/a11y-mechanical.md for the existing date patterns. Check the 13 named sites across ActivityCard, HelpWantedCard, BlogIndex, BlogDetail, Account, AccountClaim, StaffAccountClaimQueue, PersonDetail, and ProjectDetail. Done means those sites use the shared component with their needed props and retain the dateTime, absolute title, relative text, and any prefixes.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- typescript
- Domaine
- frontend
- Type d'issue
- Fonctionnalité
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- Active
- Clarté
- Clairement spécifiée
- Accessibilité débutants
- 76/100