Fix: exclude non-hideable fields from the Properties list in the view config#71729
Merged
oandregal merged 2 commits intoWordPress:trunkfrom Sep 18, 2025
Merged
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. |
t-hamano
added
[Type] Bug
oandregal
approved these changes
Sep 18, 2025
oandregal
reviewed
Sep 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
This PR hides fields with
enableHidingset to false from the hidden properties list in the view config panel.Why?
If a non-hideable field is not visible in the view, it should be excluded from the properties list. Because it can't be toggled, it doesn't make sense to keep them in the list. This will keep the list clean and let consumers hide internal fields that they may not want to expose to end users.
How?
This PR updates the condition to filter out fields with
enableHidingset tofalse.Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast