-
Notifications
You must be signed in to change notification settings - Fork 116
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
[SelectPanel] Improve messages API #3146
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 3611153 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 |
|
Waiting to merge this until the next release. The current one is getting pretty big and this PR will require some prod changes. |
@camertron how can we ensure this gets into the next release? I see we shipped PVC ~4 days ago and this wasn't included. |
What are you trying to accomplish?
Now that we've decided on a messages API for the PRC
SelectPanel
, I thought it was time to dust off this old PR and implement the new API for PVC as well.Screenshots
There should be no perceivable visual changes.
Integration
Yes. We will need to migrate existing usages of the
no_results_label
argument and theerror_content
andpreload_ error_content
slots.no_results_label
should be straightforward to identify using primer-query, and a quick search should show us wherewith_error_content
andwith_preload_error_content
are being used.Risk Assessment
What approach did you choose and why?
Anything you want to highlight for special attention from reviewers?
Accessibility
Merge checklist
Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.