Repository navigation
feat(settings): redesign General and Members - #1526
Conversation
… and leave organization Name edits go through the settings save bar while the logo still saves on upload. The data region gets its own read-only section, and the danger zone lists what deletion removes, what ages out and what is kept, matched to the organization delete purge. Members can leave the organization unless they are its only admin.
… invitation actions Members use the wide width with one line on what admins manage. A role select on each row opens a confirm strip before the change, and the row menu keeps only Remove, hidden on your own row. Invitations show when they were sent and share the same row menu with Resend (revoke and re-invite with the same role) and Revoke. The status column is gone.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 35 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Maple review🟢 Confidence 8/10 · likely safe to merge Replaces
What was checked
|
Maple review🟢 Confidence 8/10 · likely safe to merge Replaces the Organization settings tab with a General tab (save-bar name, upload-on-select logo, read-only data region, delete and leave) and rewrites Members with inline role confirm, invitation resend/revoke and loading skeletons. All UI; the two files changed since the last review only delete unused exports, and nothing blocks a merge.
What was checked
|
Maple review🟢 Confidence 8/10 · likely safe to merge Redesigns the General and Members settings tabs: the org name saves through a draft save bar, the logo uploads directly, and members get an inline role confirmation strip plus resend/revoke on invitations. The new controls only gate the UI; the API still enforces admin, so it is safe to merge.
What was checked
|
Maple review🟢 Confidence 7/10 · likely safe to merge Adds a General settings section (logo, name through the save bar, read-only data region, leave and delete) alongside the reworked Members section. Gating and draft handling look right; the new deletion copy misstates what a delete keeps.
Findings🟠 Warning · F1 ·
|
Maple review🟢 Confidence 8/10 · likely safe to merge The only change since the last review is the deletion-facts copy: the Kept row now names the retained history and settings, matching Fixed since the last review
What was checked
|
|
Preview test results and traces for the whole stack are on #1531 (all flows passed on the latest deploy). |
General (was Organization) and Members redesign.
Verification
org-membershiptests, web typecheck, local stack screenshots below. Role confirm needs a second member and is covered on the preview.Stack
Settings redesign, bottom to top: #1525 foundation, #1526 general and members, #1527 billing and usage, #1528 keys, ingestion and sampling, #1529 audit log, setup health and data platform, #1530 MCP, #1531 AI and email preferences. Bug fixes from the same audit shipped in #1524. Alerts routing is a later stack.
🤖 Generated with Claude Code
Summary by CodeRabbit