UI: Clarify public APIs and component naming, remove NoticeIntent typings#76791
Merged
UI: Clarify public APIs and component naming, remove NoticeIntent typings#76791
Conversation
|
Warning: Type of PR label mismatch To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: 0 B Total Size: 7.66 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 1d663e1. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/23507063057
|
adamsilverstein
pushed a commit
that referenced
this pull request
Mar 26, 2026
…ings (#76791) * UI: Clarify public APIs and component naming * Remove NoticeIntent prop from package export * Add CHANGELOG note for TypeScript type removal Co-authored-by: aduth <aduth@git.wordpress.org> Co-authored-by: ciampo <mciampini@git.wordpress.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
@wordpress/ui'sCONTRIBUTING.mdto clarify what's expected to be exported from the packageNoticeIntentTypeScript type from exports, consistent with the guidelines.Follow-up to https://github.com/WordPress/gutenberg/pull/75981/files#r2964670442
Why?
This largely follows and carries forward the established approach in
@wordpress/components, making it clear for future development that the approach for handling TypeScript types applies in@wordpress/uias well.Testing Instructions
Verify no references to
NoticeIntentoutside the Notice component itself.Review contributing guidelines for accuracy.