-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Components: Expose Tabs
as private API
#55327
Conversation
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.
I think this just needs a CHANGELOG (a similar PR #53262), and then it's ready to go! ✅
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.
🚀
Theme, | ||
Tabs, |
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.
We're intentionally keeping the Tabs.
namespace because we're aiming to access the components with Tabs.TabList
and Tabs.Tab
right?
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.
Correct!
Co-authored-by: Marin Atanasov <[email protected]>
What?
Exposes the new
Tabs
component as a private API.Why?
To experiment with
Tabs
in the editor as a substitute forTabPabel
implementations, or use cases whereTabPanel
wasn't suitable and custom solutions were needed instead.How?
Adding
Tabs
to the package's list of private APIsTesting Instructions
All tests should pass, but no impactful changes are being made on this PR.