DataViews: More fields, controls and operators#70567
Conversation
|
Size Change: +10.2 kB (+0.55%) Total Size: 1.87 MB
ℹ️ View Unchanged
|
|
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. |
|
Flaky tests detected in a2762cd. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/15971012635
|
Mamaduka
left a comment
There was a problem hiding this comment.
Thanks, @youknowriad and @oandregal!
I couldn't spot any regression while smoke testing the DataViews in the Site Editor.
|
I forgot about the props, it's been some time 😬 |
|
@youknowriad, I noticed that one related unit test became flaky after this got merged - https://github.com/WordPress/gutenberg/actions/runs/15999102275/job/45129358727?pr=70576. Screenshot |
|
I'm testing whether the unit tests are stable by using a fake timer: #70582 |

Closes #63646
Related #55083
Related #59745
What?
With @oandregal and others, we've been iterating on the DataViews and DataForm components to make them more powerful and enable new use-case:
We added stories to cover all of these. This PR brings this change back for everyone to use. I updated the DataViews fields that are being used in the site editor to ensure things continue to work as expected.
Testing Instructions
smoke test the dataviews usage in the site editor.