-
Notifications
You must be signed in to change notification settings - Fork 14
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
Create separator component #113
Conversation
6667a8d
to
23cb3d1
Compare
Deploying with
|
Latest commit: |
78b5ff7
|
Status: | ✅ Deploy successful! |
Preview URL: | https://6513f04d.compound-web.pages.dev |
Branch Preview URL: | https://germain-gg-divider.compound-web.pages.dev |
Initially, we'll use it just for explicit/standalone Unsure about the benefits of replacing most border decorations (for example, in menus) with a nested instance of a divider component/element, as long as we can apply semantic tokens for those border decorations. |
I'll edit the description to reflect that. |
c9951a1
to
78b5ff7
Compare
// Casting to `RefObject` as everything here should use this type. | ||
// Functions refs are not something we wish to support and string refs | ||
// are already unsupported with `forwardRef`. |
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.
If you're interested, an alternative solution that makes it possible to support function refs would be to create a new const ownRef = useRef()
, and then merge it with the forwarded ref
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.
Hmmm really cool! Didn't know that existed, thank you!
Initially, we'll use it just for explicit/standalone
<hr>
elements.There are no immediate plans to replace generic borders in components with standalone, nested divider elements.