Open digiacomo-a opened 6 months ago
Thank you for submitting a feature request. Your proposal is open and will soon be triaged by the Carbon team.
If your proposal is accepted and the Carbon team has bandwidth they will take on the issue, or else request you or other volunteers from the community to work on this issue.
Yes this isn't exported from the root, but it's exported from the root source file and so you can import them like this:
import { TYPES } from '@carbon/react/es/components/Tag/Tag';
I'm not opposed to adding these to the root exports, but we won't be able to do that until everything is converted to .ts, https://github.com/carbon-design-system/carbon/issues/12513, https://github.com/carbon-design-system/carbon/issues/16360
For now I'll add this as a subitem of https://github.com/carbon-design-system/carbon/issues/16154
I think we have to have all the export types to be named
Thank you for submitting a feature request. Your proposal is open and will soon be triaged by the Carbon team.
If your proposal is accepted and the Carbon team has bandwidth they will take on the issue, or else request you or other volunteers from the community to work on this issue.
If we upgrade to TS v5 we'd be able to just use
export type * from '@carbon/icons-react
in here
The problem
Users are often using reusable components to render Tags with different colors (type) based on some status. To achieve this, a TagType enum needs to be defined because we can not import it from carbon/react.
For instance:
The solution
Could be nice to define and export a
TagType
containing all supported types and then import it so that we can use it in our interfaces, couple of examples below.Examples
Example of an interface for Props, with tagType
Application/PAL
No response
Business priority
Low Priority = release date is not dependent on fix or not upcoming
Available extra resources
I'm happy to contribute if this change can be useful.
Code of Conduct