Skip to content

fix: missing json bodies in patch and put requests #41

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

Merged
merged 1 commit into from
Aug 18, 2021

Conversation

darora
Copy link
Contributor

@darora darora commented Aug 18, 2021

Fixes supabase/postgrest-py#7 and #30

Why are we monkey patching postgrest-py here? If we really need to hide the async reality and offer a synchronous interface, can we move it down to the postgrest-py layer so at least it's tested and kept in sync?

@fedden
Copy link
Collaborator

fedden commented Aug 18, 2021

Agreed on moving the requests/sync stuff to the postgrest-py lib.

Why are we monkey patching postgrest-py here?

It was supposed to be a temporary measure to provide an easy interface for the supabase users so we could get a release quickly out of the door, but agreed moving this to postgrest would be preferable.

elif method == "patch":
func = requests.patch
additional_kwargs = {"json": self.json}
elif method == "delete":
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm thanks!

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

Successfully merging this pull request may close these issues.

The error message: 'Error in $: not enough input' does not provide any hints on what is actually wrong.
2 participants