-
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
Interactivity API: Limit the exported APIs #58864
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: -91 B (0%) Total Size: 1.71 MB
ℹ️ View Unchanged
|
Flaky tests detected in 4eca316. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7836697941
|
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.
LGTM! 🙂
What?
Epic: #56803
Makes the
@wordpress/interactivity
module to export only the APIs that will be public on WordPress 6.5.Only the following functions should be exposed publicly:
getConfig
,getContext
,getElement
,store
,useCallback
,useEffect
,useInit
,useLayoutEffect
,useMemo
,useRef
,useState
,useWatch
, andwithScope
.The rest of the APIs are accessible only through the function
privateAPIs
, meant to be used exclusively internally.PS: You can notice that
getConfig
doesn't appear in the PR changes: it's part of #58749.