-
Notifications
You must be signed in to change notification settings - Fork 38
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
jsonDecode on Empty String #131
Comments
@MelbourneDeveloper: I'm not sure if this is relevant for the |
Ah, sorry! I assumed the Supabase library depended on this library, but it turns out it doesn't. I will log this with Supabase. Thanks! |
Just to explain, the package was PostgREST. I misread the package name, and that's why this ended up here. I moved the issue here for people Googling this |
I just upgraded to http ^1.1.0. It looks like it's not compatible with the Postgres SDK V1.5.0
The endpoint returns 204 with an empty body, but the code tries to parse the response.
The problem is happening in
_parseResponse
. You can see that the body is empty string here.It was a query for a table with an
eq
on the ID column. The method isPATCH
. The content length here is actually 0, so it should be hitting a different code path I would say.The text was updated successfully, but these errors were encountered: