Body types other than JSON are improperly handled when invoking a function

[encima]

When invoking a function, the content type is detected and set as a header but the httpx call sets the json property but, for strings, this would be content.

[grdsdev]

Thanks for pointing that out, will have a look

[silentworks]

@encima can you provide a test case where the current setup breaks? preferably a test case with code example.

[encima]

sure, will provide an example on Monday!

any function that takes a string will break as it will be encoded as JSON

[encima]

aaand it seems there was already a fix for it!

but, to stay a person of my word:

  fc = AsyncFunctionsClient("https://<project_ref>.functions.supabase.co", {})
  res = await fc.invoke("payment-sheet", {"body": "this is not json, but a string"})

Using this (before the fix) would set the content-type header to plain but the body itself would be passed in under the json parameter so the edge function would receive the string as JSON encoded

[silentworks]

@encima yeah a fix was made by @juancarlospaco on the day you reported it. We will get the fix merged in and get a new release out soon.

Also thanks for providing the example above.