-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
DataViews: Type the ViewList component #61246
Conversation
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: +12 B (0%) Total Size: 1.74 MB
ℹ️ View Unchanged
|
2d97093
to
68f3265
Compare
Flaky tests detected in 68f3265. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/8908354138
|
0168d6f
to
e9f311e
Compare
[ onSelectionChange ] | ||
); | ||
|
||
const getItemDomId = useCallback( | ||
( item ) => ( item ? `${ baseId }-${ getItemId( item ) }` : undefined ), | ||
( item?: Item ) => ( item ? `${ baseId }-${ getItemId( item ) }` : '' ), |
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.
Returning an empty string instead of undefined
changes the behavior of getItemDomId
breaking the keyboard navigation. Fix at #61478
Related #55083
Follow-up to #61185
What?
The DataViews package is a types heavy package. There's a lot of structures that need to be documented properly. So this continues the effort to add explicit types to the package. This PR focuses on typing the ViewList component which forces us to enhance the "View" type.
Testing instructions
There's no functional change, it's essentially a code quality + documentation change.