-
Notifications
You must be signed in to change notification settings - Fork 542
fix: FEAT: Array column should be filterable #1385
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
Conversation
|
@rishi-raj-jain is attempting to deploy a commit to the Rowy Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
|
Can you take a look? I've extended every method in firestore for arrays: https://firebase.google.com/docs/firestore/query-data/queries#array_membership Works locally just as fine. |
|
@rishi-raj-jain First of all, thank you for the efforts. Second, the PR needs to be opened against develop. You'll need to rebase. Third, this PR isn't working for all cases. To reproduce, use "not-includes" as the operator. I believe it isn't working because the translation from rowy/src/hooks/useFirestoreCollectionWithAtom.ts Lines 386 to 398 in b2983f4
|
|
Thanks for pointing that out. |
Yes
The name of your branch can be anything. It doesn't have to be develop. Let's say your branch name is rishi. The PR will be from rishi to develop. However, rishi should have all the commits from rowy's develop plus your new commits. Otherwise, there will be merge conflicts which we can see right now. There are different ways to do this.
|
|
Thanks for the answers. I do realize it's not the same but the branch. I figured out that in and not-in don't work when we want to filter when the filter value is an array itself. Only, ==, !=, array-contains and array-contains-any are the supported methods as I gather from that link + testing in a simple demo.js file. |
|
Creating a fresh PR. |
fix: #1382
/claim #1382