-
Notifications
You must be signed in to change notification settings - Fork 538
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
export FilteredActionList #4816
Conversation
🦋 Changeset detectedLatest commit: 839501c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
size-limit report 📦
|
packages/react/src/index.ts
Outdated
@@ -206,3 +206,6 @@ export type {PageHeaderProps} from './PageHeader' | |||
export {SSRProvider, useSSRSafeId} from './utils/ssr' | |||
export {default as sx, merge} from './sx' | |||
export type {SxProp} from './sx' | |||
|
|||
export {FilteredActionList} from './FilteredActionList' | |||
export type {FilteredActionListProps} from './FilteredActionList' |
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.
Question for reviewer:
Should we export this from experimental
instead? It isn't really experimental because it's been what powers SelectPanel from the start.
But if we want to treat this as a temporary solution, then it feels okay
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'm down with experimental if it means we won't have to go through a deprecated flow 😂 But if we still have to go through that, then stable is fine 👍
(Separate from this PR) this could be a good example for spots where an unstable_*
convention could help out without having to couple things to entry points
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.
My only comment is that it would be great to treat it as an experimental/unstable component so that we don't have to worry about semver in case if we need to make any changes for the SelectPanel remediation.
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.
Valid, moved it to experimental
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.
Left a comment! Let me know your thoughts!
Closes #4840
Changelog
While work on SelectPanel is on-going, there is a gap between the design of SelectPanel and the implementation in PRC.
In order to fill the gap with a temporary solution, developers can opt to build a custom implementation. Exporting FilteredActionList, which lies under SelectPanel, would help.
More context on Slack: https://github.slack.com/archives/CSGAVNZ19/p1722543563922769?thread_ts=1722472095.221459&cid=CSGAVNZ19
Rollout strategy
Merge checklist