Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Export all types from Clay #5608

Open
matuzalemsteles opened this issue Jun 28, 2023 · 0 comments
Open

Export all types from Clay #5608

matuzalemsteles opened this issue Jun 28, 2023 · 0 comments
Labels
comp: clay-components Issues related to Clay components. (e.g ClayCard, ClayLabel...) rfc Similar to the RFC that are used in React.js, Ember.js, Gatsby.js and Rust, but to mark problems tha

Comments

@matuzalemsteles
Copy link
Member

Thread Slack

The idea is that we can export all types of Clay components with the component name prefix to avoid name conflict. This makes it easy for other developers to extend the types into their own components.

As a temporary solution while we evaluate the priority of this, developers can get the component types using React.ComponentProps which is also a recommendation for this.

Jira Ticket LPS-188001
@matuzalemsteles matuzalemsteles added rfc Similar to the RFC that are used in React.js, Ember.js, Gatsby.js and Rust, but to mark problems tha comp: clay-components Issues related to Clay components. (e.g ClayCard, ClayLabel...) labels Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
comp: clay-components Issues related to Clay components. (e.g ClayCard, ClayLabel...) rfc Similar to the RFC that are used in React.js, Ember.js, Gatsby.js and Rust, but to mark problems tha
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@matuzalemsteles