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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: joshualip-plaudit <[email protected]>
Co-authored-by: manzoorwanijk <[email protected]>
Co-authored-by: swissspidy <[email protected]>
Co-authored-by: t-hamano <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @joshualip-plaudit! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

I don't know how to add the "props-bot" label, but I linked my account

So... Tests failed because they timed out while downloading themes. How do I go about restarting them?

@manzoorwanijk I'll make the changes that you requested to try to fix the git history later today (although, I don't know if that's going to be recoverable without me remaking the branch + changes from scratch).

Wrt to the "replace react imports with React.ReactNode" suggestions, I'm curious as to how switching from a type import to React.ReactNode changes anything? React is still being "imported" (in quotes because it's not the same import process as an import statement), but now we're relying on an implicit "import" of a global namespace.

Update: Fixing the history loss is done. I wound up recreating the branch and separating the rename and edit steps for the files that had issues into two commits

@manzoorwanijk Ping on this one? I'm unsure what you mean by, "move this to an inline types.ts file". I was able to resolve the history issue without relying on an external file, so I don't think it's needed anymore.

Also, I am still curious why using React.ReactNode is preferred over using a typed import. If it's a style thing, I can change it, I'm just wondering if there is an additional concern because I use that import style in my own projects.

why using React.ReactNode is preferred over using a typed import.

Since React is available globally, it saves us an import statement when used instead of using the type import.

Thanks for the clarification! I've made the requested changes.

Nice, this will make #64799 obsolete