-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
DataViews: fix bug on operators count for table layout #57048
Conversation
Size Change: -2 B (0%) 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!
I'm wondering though if we expect more props in filterBy
. Should we make this top level prop?
Flaky tests detected in 2687f9d. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7206580839
|
It's going to depend on how we evolve it UI-wise. In this mockup, there were operators and selections (any or all), which would be separate keys under |
Part of #55083
Related to #55100
See #56479 (comment)
What?
Fixes a bug by which the filters for a field couldn't be disabled in the
table
layout.Testing Instructions
packages/edit-site/src/components/page-pages/index.js
and, in the line 267, remove all the operators present:table
layout, click on the status column header and verify there is no filter. Check that there is no status filter in the filters menu (top-level row).Gravacao.do.ecra.2023-12-14.as.09.56.38.mov