fix(supabase): fixed 'in'-filter when used inside 'or' #6652
Conversation
🦋 Changeset detectedLatest commit: 94e82ac The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for refine-doc-live-previews ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
| @@ -2073,3 +2073,77 @@ nock("https://iwdfzvfqbtokqetmbmbp.supabase.co:443", { | |||
| 'h3=":443"; ma=86400', | |||
| ], | |||
| ); | |||
|
|
|||
| nock("https://iwdfzvfqbtokqetmbmbp.supabase.co:443", { | |||
There was a problem hiding this comment.
Let's please record the actualy request. Here we are providing the mock data, without making the request, and we are testing it based on the data provided by us. It's not really testing anything.
There was a problem hiding this comment.
yeah, already thought so... is there a reason why the other tests also don't make actual requests or am i reading something wrong?
nevertheless will change to a real request
If a
inFilter is used inside aLogicalFilterit is not parsed correctly to supabase. See #6651PR Checklist
Please check if your PR fulfills the following requirements:
Bugs / Features
What is the current behavior?
Filter get parsed incorrectly
or=(id.in.1,2,4)What is the new behavior?
Filter get parsed correctly
or=(id.in.("1", "2"))fixes (#6651)
Notes for reviewers