Fix low-contrast dark-theme text and Users row overlap on 6 admin pages - #24
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Analytics, Press Releases, Live Streams, Audit Reports, Procurement,
and Users were built with dark-theme classes (text-white, text-green-
200/*, bg-white/5, border-white/10) assuming a dark page background,
but the admin content area is actually light (bg-slate-50) — headings,
subtitles, stat labels, search placeholders, and pagination text were
all rendering nearly invisible (white/pale-green on white). Converted
all six to the light theme already used correctly elsewhere in the
admin panel (LGA Approvals, Wards, Payments, Allocations).
The Users list row had the same non-stacking layout bug fixed earlier
on LGA Approvals — avatar, name, badges, and Suspend/Ban buttons were
forced into one non-wrapping row, so on mobile names and emails
truncated to a single character ("K…", "ke…") and buttons crowded the
text. Now stacks properly on narrow screens.
Also found the root cause of a stray corrupted byte discovered while
editing press-releases: the previous session's arrow-mojibake fix
(sed replacing "â†" with "←") left a dangling C1 control byte (U+0090)
immediately after the arrow in 5 files, invisible in normal viewing
but preventing exact-string edits on those lines. Fixed at the byte
level and confirmed zero remaining control-character corruption
across the whole app/ tree.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UPJE5cNDtQ4j7yeg9Xjtxw
dprograma
force-pushed
the
claude/lga-auth-e2e-test-ocez8x
branch
from
July 24, 2026 19:01
5743cb2 to
c514792
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
text-white,text-green-200/*,bg-white/5,border-white/10), but the actual admin content area is light (bg-slate-50) — headings, subtitles, search placeholders, stat labels, and pagination text were rendering nearly invisible. Converted all six to the light theme convention already used correctly by LGA Approvals, Wards, Payments, and Allocations.sedreplacingâ†with←) left a stray invisible control byte (U+0090) immediately after the arrow character in 5 files — harmless to rendering but corrupting the source enough to block exact-string edits on those lines. Fixed at the byte level; confirmed zero remaining control-character corruption across the wholeapp/tree.Test plan
npx tsc --noEmit— cleannpx eslinton every changed file — no new issues (remaining errors are the same pre-existingreact-hooks/set-state-in-effectwarnings already present on these files)npx playwright test --project=api— 452/452 passedGenerated by Claude Code