-
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
Remove PostSlugCheck and PostSlug unused components #67414
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. |
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.
Makes sense. I was wondering the same when I recently refactored one of these components.
Makes sense to me. |
Size Change: -151 B (-0.01%) Total Size: 1.83 MB
ℹ️ View Unchanged
|
Flaky tests detected in 3348936. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12082472565
|
I have no memory of why I added these 😆 |
Co-authored-by: ntsekouras <[email protected]> Co-authored-by: Mamaduka <[email protected]> Co-authored-by: youknowriad <[email protected]>
Co-authored-by: ntsekouras <[email protected]> Co-authored-by: Mamaduka <[email protected]> Co-authored-by: youknowriad <[email protected]>
What?
I was working on another PR and noticed that
PostSlugCheck and PostSlug
components seem to have been implemented in very early FSE stages by @felixarntz here and are using a custom post type support (slug
). It doesn't make sense to have these since they could only work if a post type registers this custom support value.They are not used in our codebase and it seems are not consumed by anyone (1, 2).
Also linking my slack question in core-editor.
Testing Instructions