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: Filter "is not empty" doesn't work as expected #1459

Closed
janvi01 opened this issue Nov 1, 2023 · 8 comments
Closed

Bug: Filter "is not empty" doesn't work as expected #1459

janvi01 opened this issue Nov 1, 2023 · 8 comments
Assignees
Labels
bug Something isn't working priority-high

Comments

@janvi01
Copy link
Contributor

janvi01 commented Nov 1, 2023

Describe the bug
While applying the filter "is not empty" on any column, either it just keeps loading or gives an error.

To Reproduce
Steps to reproduce the behavior:

  1. Apply the filter "is not empty" operator inside the filter modal in any column of your table.

Expected behavior
It should show the data according to the filter.

Screenshots

Screenshot 2023-11-01 at 4 40 15 PM Screenshot 2023-11-01 at 4 40 54 PM
@janvi01 janvi01 changed the title Bug: Filter "is not empty" doesn't works as expected Bug: Filter "is not empty" doesn't work as expected Nov 1, 2023
@janvi01
Copy link
Contributor Author

janvi01 commented Nov 1, 2023

@Chadha93 I would like to work on this.

@MiirzaBaig
Copy link

Can i work on this issue..?
I hope i can provide minimalistic solution to it, upon further discussion...

@Chadha93 Chadha93 added bug Something isn't working priority-high labels Dec 5, 2023
@Chadha93
Copy link
Member

Chadha93 commented Dec 5, 2023

@Chadha93 I would like to work on this.

Hi @janvi01, sure feel free to make a PR, I can confirm this issue.

@Chadha93
Copy link
Member

Chadha93 commented Dec 5, 2023

@janvi01 Here is a more detailed log of the bug: {"name":"FirebaseError","message":"initializeFirestore() has already been called with different options. To avoid this error, call initializeFirestore() with the same options as when it was originally called, or call getFirestore() to return the already initialized instance.","stack":"FirebaseError: initializeFirestore() has already been called with different options. To avoid this error, call initializeFirestore() with the same options as when it was originally called, or call getFirestore() to return the already initialized instance.","code":"failed-precondition"}.

@bofeiw
Copy link
Contributor

bofeiw commented Dec 5, 2023

Potentially related to: #1390 and #1482

@janvi01
Copy link
Contributor Author

janvi01 commented Dec 11, 2023

I have started working on this.

@il3ven
Copy link
Contributor

il3ven commented Dec 11, 2023

I have started working on this.

@janvi01 Thanks for reporting this bug. I saw your comment after I opened a PR for this.

@janvi01
Copy link
Contributor Author

janvi01 commented Dec 12, 2023

oh no problem @il3ven

@harinij harinij closed this as completed Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-high
Projects
None yet
Development

No branches or pull requests

6 participants