Experiment: Integrate useView in content types lists#78197
Merged
Conversation
ntsekouras
added
[Type] Experimental
47 tasks
|
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: +1.46 kB (+0.02%) Total Size: 7.93 MB 📦 View Changed
ℹ️ View Unchanged
|
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
2 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?
Part of: #77600
This PR integrates the
useViewhook to persist some view changes in the content types' lists (taxonomies/post types). It also syncs thesearch and pageparams in the URL.Noting that
search and pageare not preserved in the persistence layer, so when navigating through the tabs those params are reset. I think that's fine for this iteration and we can revisit if something like this is needed.Video (after)
Screen.Recording.2026-05-12.at.2.01.05.PM.mov
Testing instructions
Content typesexperiment.Settings → Content typesand make some changes in the view of either entity (taxonomies/post types) like re-ordering of a field or adding/hiding a field.Reset viewand observe that works as expectedUse of AI Tools
Opus 4.7 with direction, changes and review