RPC call cannot set headers in 1.0.0-dev.4

[dsyrstad]

Prior to 1.0.0, I was able to set headers on an rpc request (somewhat awkwardly):

  builder = client
        .rpc('fn_taking_single_jsonb_param', params: request);
  builder.headers['Prefer'] = 'params=single-object';
  await builder.execute();

I was able to do this because PostgrestBuilder previously exposed headers. The headers are now private and I can find no way to set them. PostgrestClient still seems to expose headers, but I don't have access to it via SupabaseClient.

See https://postgrest.org/en/stable/api.html#calling-functions-with-a-single-json-parameter for the params=single-object value.

[bdlukaa]

@dshukertjr could custom headers be added to rpc as well?

[Vinzent03]

It was already requested here. I think we should add this.

[bdlukaa]

Duplicate of #179

[dsyrstad]

@bdlukaa @Vinzent03 I just want to clarify that this issue is a blocker for me because what used to be doable pre-1.0.0 is no longer doable. Being able to use the PostgREST Prefer: params=single-object header is required for me to move to 1.0.0.

Issue #179 is about adding non-PostgREST headers. I think this should be fixed before the 1.0.0 release, but until then I can use this workaround: #179 (comment).

#179 should have been reported against this repo, rather than the supabase-flutter repo.

[Vinzent03]

@dsyrstad We are collecting all issues in supabase-flutter. Technically, the issue belongs to postgrest-dart.

@dshukertjr I think we should enforce this more or at least mention in the README. It's a bit confusing if nobody knows.

[dsyrstad]

@Vinzent03 I don't think the issue belongs in postgrest-dart because I can modify the headers if I use the PostgrestClient directly. It's the SupabaseClient which made the headers private and broke things for me.

[dshukertjr]

@dsyrstad
It sounds like what you really want is a handy way of setting Prefer: params=single-object header. I have opened an issue on js library so that we could have a discussion about it. Feel free to chime in on the js issue as you like!

I will re-open this issue for now.

[dsyrstad]

@dsyrstad It sounds like what you really want is a handy way of setting Prefer: params=single-object header.

@dshukertjr That would be even better. If you're considering that, maybe you should also add: Prefer: params=multiple-objects https://postgrest.org/en/stable/api.html#bulk-call. I've made the same comment over on supabase/postgrest-js#304.