Skip to content

Phase 4.1: Remaining Components (Batch 1) — Refactor with ProfileAvatarDisplay #5144

@coderabbitai

Description

@coderabbitai

Overview

Refactor a first batch of remaining components to use ProfileAvatarDisplay, focusing on lower-risk, homogeneous patterns (lists/cards with simple avatar usage).

Comprehensive Implementation Plan: #5130 (comment)

Estimated Effort

⏱️ 2 hours (of the 6 hours total for Phase 4)

Dependencies

🔗 Depends on: Phase 1 (ProfileAvatarDisplay Foundation) being merged

Candidate Files (to confirm during PR prep)

  • Components with simple {image ? <img> : <Avatar>} patterns and minimal custom error handling
  • Low coupling to upload/edit flows

Implementation Tasks

  • Replace conditional image/Avatar rendering with ProfileAvatarDisplay
  • Ensure alt text uses i18n keys
  • Preserve existing className/layout
  • Add/adjust unit tests for each touched component

Acceptance Criteria

✅ All batch components use ProfileAvatarDisplay
✅ No UI regressions (layouts unchanged)
✅ i18n compliance for alt/aria strings
✅ Tests updated and passing
✅ No TypeScript or ESLint issues

Notes

This is Batch 1 of 3 in Phase 4; aim for ~5–6 components depending on size/complexity.

Metadata

Metadata

Labels

good first issueGood for newcomerssecuritySecurity fixui/uxissue related and being worked with the figma file of the Admin UI

Type

No type

Projects

Status

Backlog

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions