Skip to content

chore: add Base UI migration RFC#730

Open
rohanchkrabrty wants to merge 5 commits intomainfrom
add-base-ui-migration-rfc
Open

chore: add Base UI migration RFC#730
rohanchkrabrty wants to merge 5 commits intomainfrom
add-base-ui-migration-rfc

Conversation

@rohanchkrabrty
Copy link
Copy Markdown
Contributor

@rohanchkrabrty rohanchkrabrty commented Apr 6, 2026

Summary

  • Add RFC document for migrating Apsara design system from Radix UI to Base UI

Preview

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 6, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
apsara Ready Ready Preview, Comment Apr 6, 2026 8:31pm

@rohanchkrabrty rohanchkrabrty removed the request for review from paanSinghCoder April 6, 2026 20:02
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 6, 2026

📝 Walkthrough

Walkthrough

Adds an RFC proposing migration of the Apsara design system from Radix UI/Ariakit/Cmdk/Sonner to Base UI primitives. Describes problems with the multi-library composition (e.g., focus-scope conflicts), a phased migration scope (initially 18 of 52 components), cross-cutting API/behavior changes (examples: asChildrender, ContentPopup/Panel, OverlayBackdrop, Positioner, detached triggers), component-specific API differences, a component mapping table, estimated implementation/testing/migration effort, and migration references. No code or exported/public API changes.

Suggested reviewers

  • rohilsurana
  • rsbh
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore: add Base UI migration RFC' accurately summarizes the main change—adding an RFC document for the Base UI migration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check ✅ Passed The pull request description accurately reflects the changeset, which adds an RFC document for the Apsara design system migration from Radix UI to Base UI.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
docs/rfcs/001-base-ui-migration.md (1)

84-84: Quantitative claim needs evidence or scope qualifier.

Line 84 states package size will reduce by 50%, but there’s no measurement context (bundle target, baseline, tooling). Add a short note on how this was estimated or label it as preliminary.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/rfcs/001-base-ui-migration.md` at line 84, The statement "**Package
Size:** The required package size would reduce by 50%" lacks measurement
context; update the RFC by either (a) adding a short note describing how this
estimate was obtained (baseline bundle, target build, tooling used, and whether
minified/gzipped), or (b) rewording to a qualified claim (e.g., "preliminary
estimate ~50% reduction based on [tooling/target]") so readers know the scope
and confidence of the number; edit the line containing "**Package Size:**"
accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/rfcs/001-base-ui-migration.md`:
- Line 4: The RFC's status header currently reads "Status: Completed" but this
is an open proposal; update the status field in the document header (the
"Status:" line in the RFC text) to a tentative state such as "Proposed" or "In
Review" so it reflects that the migration is still under consideration; ensure
the change is applied to the top-level Status: field in the RFC content (replace
"Status: Completed" with "Status: Proposed" or "Status: In Review").
- Line 271: The component mapping table erroneously maps Tooltip to Sonner;
update the Tooltip row to map to the correct library used in the codebase
(change the Sonner entry to `@base-ui/react` or "Base UI") so Tooltip is
associated with Base UI instead of Sonner; locate the table row containing the
"Tooltip" label and replace its mapped library from "Sonner" to "@base-ui/react"
(or "Base UI") to match the actual implementation and the earlier note that
Sonner is used for Toast.

---

Nitpick comments:
In `@docs/rfcs/001-base-ui-migration.md`:
- Line 84: The statement "**Package Size:** The required package size would
reduce by 50%" lacks measurement context; update the RFC by either (a) adding a
short note describing how this estimate was obtained (baseline bundle, target
build, tooling used, and whether minified/gzipped), or (b) rewording to a
qualified claim (e.g., "preliminary estimate ~50% reduction based on
[tooling/target]") so readers know the scope and confidence of the number; edit
the line containing "**Package Size:**" accordingly.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f74fa748-c088-470c-b5f6-580368dae04a

📥 Commits

Reviewing files that changed from the base of the PR and between 2eabd18 and 42e4997.

📒 Files selected for processing (1)
  • docs/rfcs/001-base-ui-migration.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant