-
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
Components: Hide private READMEs from handbook #60003
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.71 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.
Looks good, thanks for spotting!
Haven't checked, but It's likely that these were exposed in the middle of development, and then unexposed before merging, but without us cleaning up the manifest.
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.
👍
Noting for posterity: It turns out that the manifest.json handling is non-destructive, so removing entries from the file will not automatically remove it from the published handbook. We currently need to get someone from the Meta team to remove them manually. And if we ever need redirects, we can declare them here. |
What?
Removes private component docs that were unintentionally leaking into the public Block Editor Handbook:
Why?
It is unnecessary and confusing to list still-private components in the handbook, since they are not publicly available yet.
Testing Instructions
This can only be tested by deploying.
Related
For some reason, we can see some published component READMEs that are not in the manifest.json:
I'm guessing this is some kind of caching issue? I don't see anything suspicious in the code responsible for handling the manifest.json, but we may have to escalate this issue if it doesn't resolve in the next deploy.