-
-
Notifications
You must be signed in to change notification settings - Fork 132
[core] Remove useComponentRenderer #2055
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[core] Remove useComponentRenderer #2055
Conversation
atomiks
commented
Jun 3, 2025
- I have followed (at least) the PR section of the contributing guide.
commit: |
Bundle size reportTotal Size Change: Show 36 more bundle changes@base-ui-components/react parsed: |
✅ Deploy Preview for base-ui ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ref: forwardedRef, | ||
props: [elementProps, { id }], | ||
props: [{ id }, elementProps], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This actually doesn't matter as elementProps
can't contain id
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sidenote on perf, I've been looking into having uRE automatically handle merging componentProps
minus render
& className
into props, it would avoid destructuring into elementProps
for some components (those that don't extract more props out of componentProps
). The only thing stopping me right now is that some components don't have elementProps
as the final element in the props
array.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@michaldudak yeah, but each component was doing something different - just changed to be the most consistent