This repository was archived by the owner on Jul 6, 2026. It is now read-only.
fix(web): admin role not recognized (PascalCase) — normalize in AdminGuard#86
Merged
Conversation
The API serializes the user role as PascalCase ("Admin"/"Enterprise"/"Freelancer").
AdminGuard checked `role === "admin" || role === 2`, so a real admin was shown the
"Admin access required" screen. Route both raw role comparisons through normalizeRole
(case/format-insensitive), matching the rest of the app.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
enes.admin@loopless.dev(Role=Admin in DB + KC) was shown "Admin access required" on the admin host.Root cause: the API returns
user.roleas PascalCase"Admin", butAdminGuard.isAdmin()checkedrole === "admin" || role === 2→ false. Same casing class as the earlier AppNavigation fix.Fix: route the AdminGuard check (and the getting-started checklist's enterprise check, same raw pattern on
user.role) throughnormalizeRole().Verified:
tsc✓,next lint0 warnings ✓. Frontend-only.