fix: rpc call returns PostgrestFilterBuilder #50
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes supabase/supabase-swift#110
What kind of change does this PR introduce?
Changes the return value of the
rpc
call to returnPostgrestFilterBuilder
instead ofPostgrestTransformBuilder
, which allows for use of the filter functions like.neq
,.eq
, etc.This appropriately changes the return value to be the same as in postgrest-js
What is the current behavior?
At the moment, an
.rpc
call would returnPostgrestTransformBuilder
which only has the available methodsselect
,order
,limit
,range
.Please link any relevant issues here.
supabase/supabase-swift#110
What is the new behavior?
The
.rpc
call returns aPostgrestFilterBuilder
object.Additional context
New filter options compared to the other screenshot in the linked issue.
Tested a couple of filters and seems to work fine returning the expected data.