fix(console): polished, localized 'Assigned Users' management (real-user UX pass)#2002
Merged
Conversation
…mission sets UX review (from a real admin's POV) found the prior generic-related-list embed unusable: it showed a raw user_id (couldn't tell who held a seat), English text in a Chinese UI, and a dev-flavored '[ObjectStack] AI-seat cap reached…' banner. Rewrite AssignedUsersSection as a people-first widget over sys_user_permission_set: - resolves each user_id to a real name/email (fetch+join sys_user; no lookup- timing dependence) → you can see WHO holds the seat - localized (zh/en via detectLocale): title, count, Add, Remove, empty state - friendly inline cap message (amber, no [Tag] prefix): maps the server cap error to 'AI 席位已用完(N/N)…' - people rows (avatar initial + name + email) with inline remove; '添加用户' opens the reusable RecordPickerDialog (multi-select) The generic add-by-picker engine (spec RecordRelatedListProps.add) still ships as the platform capability; this is the polished surface for the high-value case. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
❌ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
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
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.
A UX review (from a real admin's POV) of the just-shipped permission-set "Assigned Users" found it not understandable: it showed a raw
user_id(couldn't tell who held a seat), English text in a Chinese UI, and a dev-flavored[ObjectStack] AI-seat cap reached…banner.Rewrites
AssignedUsersSectionas a people-first, localized widget oversys_user_permission_set:sys_user; no lookup-timing dependence) → you can see WHO holds a seatdetectLocale): title, count, Add, Remove, empty state[Tag]prefix): maps the server cap error → "AI 席位已用完(N/N)…"RecordPickerDialogBrowser-verified (objectos-ee, cap=1): the
ai_seatset shows "已分配用户 1人" + Dev Admin/admin@objectos.ai; adding at cap → the amber localized message; remove (×) + add → the new user gains the seat and shows with name/email.The generic add-by-picker engine (#1999 + framework#2324) still ships as the platform capability; this is the polished surface for the high-value case. Follow-ups (separate): hide the irrelevant CRUD matrix for seat-type sets, a friendly label for
ai_seat, and a dedicated AI-seat page.🤖 Generated with Claude Code