Skip to content
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

[Bug Report][3.6.8] No item matches when all headers use custom filter #19970

Open
hitochan777 opened this issue Jun 7, 2024 · 1 comment
Open

Comments

@hitochan777
Copy link

hitochan777 commented Jun 7, 2024

Environment

Vuetify Version: 3.6.8
Vue Version: 3.4.27
Browsers: Chrome 125.0.0.0
OS: Linux x86_64

Steps to reproduce

Use filter key for all headers in v-data-table.

Expected Behavior

Items should match according to filter functions.

In the current doc of Vuetify 3, it says intersection: There is at least one match from the custom filter, and all columns match the custom key filters.
I am using default filter-mode which is intersection so the behavior seems to follow what the docs says.
However, in the doc of Vuetify2, it says intersection: There is at least one match from the default filter, AND all custom column filters match.
If I understand correctly, they are supposed to behave the same if I don't specify custom filter and let it use default filter.

One workaround is to use every for filter-mode, but I just want to know if the current behavior is intentional or not . If it is intentional it would be better if the documentation gets more clarification.

Actual Behavior

No item matches even when there are actually matches. In Vuetify2, they matches properly.

Reproduction Link

Vuetify2
Vuetify3

@hitochan777 hitochan777 changed the title [Bug Report][3.6.8] When all headers use custom filter no item matches [Bug Report][3.6.8] No item matches when all headers use custom filter Jun 8, 2024
@hitochan777 hitochan777 reopened this Jun 8, 2024
@partment
Copy link

partment commented Jun 16, 2024

When all columns use custom filter, have to use filter-mode="union" to match properly.
On the other hand, If at least one column don't use custom filter, use the default filter-mode which is intersection to match properly.
Quite frustrating when migrating from v2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants