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.

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

fix(react): Make RadioItem public #1668

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

stephenmathieson
Copy link
Member

An application I'm working on requires using the RadioItem type directly, but the type is not exported from the package's entrypoint. This patch makes RadioItem part of the public API.

Previously, to get access to RadioItem, users would have to:

import {RadioItem} from "@deque/cauldron-react/lib/components/RadioGroup"

This is brittle (will break if we rename files/etc.) and doesn't look nearly as nice.

An application I'm working on requires using the `RadioItem` type directly, but the type is not exported from the package's entrypoint. This patch makes `RadioItem` part of the public API.

Previously, to get access to `RadioItem`, users would have to:

```ts
import {RadioItem} from "@deque/cauldron-react/lib/components/RadioGroup"
```

This is brittle (will break if we rename files/etc.) and doesn't look nearly as nice.
@stephenmathieson stephenmathieson requested a review from a team as a code owner September 10, 2024 19:06
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1668.d15792l1n26ww3.amplifyapp.com

Copy link
Member

@scurker scurker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We typically have not been exporting the types from components, and don't really think we should do one offs without thinking about how this impacts our public api. Do you mind writing an RFC proposing why we should make this change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants