-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
useSelect: Make deps optional param. #66187
base: trunk
Are you sure you want to change the base?
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: 0 B Total Size: 1.81 MB ℹ️ View Unchanged
|
Flaky tests detected in d812f9c. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11587936170
|
The function useSelect( store: StoreDescriptor ): StoreSelectors;
function useSelect<T>( mapSelect: MapCallback<T>, deps: unknown[] ): T; Is it possible to express this also in JSDoc? Two signatures, no optional params. |
@jsnajdr Thank you for your review! I tried to get the following signatures built using
|
What?
Update jsdoc to explicitly state that deps is optional.
Why?
The deps parameter in useSelect is optional, allowing usage such as const { getSettings } = useSelect( myCustomStore ). However, in the built type information, deps is set as a required parameter, causing this code to throw an error when using TypeScript. Therefore, we will revise the JSDoc to modify the generated type information.
Testing Instructions