-
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
Documentation: PostPendingStatus + PostPendingStatusCheck editor components #61970
Documentation: PostPendingStatus + PostPendingStatusCheck editor components #61970
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. |
…onents (WordPress#61970) * Add PostPendingStatus editor component JSDocs * Add PostPendingStatusCheck editor component JSDocs * Auto-generate editor docs for PostPendingStatus additions * Refine PostPendingStatusCheck component JSDocs * Auto-generate editor docs for PostPendingStatusCheck updates
…onents (WordPress#61970) * Add PostPendingStatus editor component JSDocs * Add PostPendingStatusCheck editor component JSDocs * Auto-generate editor docs for PostPendingStatus additions * Refine PostPendingStatusCheck component JSDocs * Auto-generate editor docs for PostPendingStatusCheck updates
What? & Why?
Addresses two items in #60358
Adding documentation to existing editor components can help with any of the following:
How?
Add a JSDoc comment to the
PostPendingStatus
andPostPendingStatusCheck
components and runnpm run docs:build
to populate theREADME
with the newly added documents.