-
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
Convert dom-ready package to TypeScript #67671
base: trunk
Are you sure you want to change the base?
Convert dom-ready package to TypeScript #67671
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.84 MB ℹ️ View Unchanged
|
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 from a code perspective, but I'm still getting familiar with WPCS flavor of typescript (e.g. explicitly returning : void
in the function definition)
Flaky tests detected in cee0bd9. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12515978392
|
Supercedes #67571, which got closed after I deleted my fork 🤦
What?
Converts the dom-ready package to TypeScript
Why?
To improve DX for the package
How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast