Skip to content
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

Do not encode json request body #6

Merged
merged 4 commits into from
Dec 29, 2024
Merged

Do not encode json request body #6

merged 4 commits into from
Dec 29, 2024

Conversation

zoedsoupe
Copy link
Collaborator

Problem

The problem is that the lib was encoding the request body json twice, so it was being sent as a string and PostgREST was decoding as a raw string instead of a json itself.

Solution

Stops to encode the request body at all and let the Finch http client decide to do it once, also it handle correctly media types headers accept

Rationale

@zoedsoupe
Copy link
Collaborator Author

this closes #2 and also updates elixir to v1.18 (with improvements in the type system) and also init a supabase local project

@zoedsoupe zoedsoupe merged commit f048c64 into main Dec 29, 2024
1 check passed
@zoedsoupe zoedsoupe deleted the fix/insert-broken branch December 29, 2024 23:18
@zoedsoupe zoedsoupe linked an issue Dec 30, 2024 that may be closed by this pull request
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.

Insert broken
1 participant