Use additional headers from SupabaseClient into GotrueClient.

[tartard]

What kind of change does this PR introduce?

Feature

What is the current behavior?

When we instantiate SupabaseClient it is possible to specify additional headers to use in any API request :

supabase-js/src/SupabaseClient.ts

Line 44 in c5310d6

* @param options.headers Any additional headers to send with each network request.

These headers don't seem to be actually used at all.

Gotrue allows to specify the audience of the users during requests, by setting a header 'X-JWT-AUD' containing the audience, but we cannot use this feature yet because when SupabaseClient instantiates the GotrueClient, it doesn't forwards the custom headers to it.

What is the new behavior?

When SupabaseClient instantiates the GotrueClient, it forwards the custom additional headers to the GotrueClient. It is now possible to set the 'X-JWT-AUD' header in every request to Gotrue.

[kiwicopple]

Nice work @tartard - this is great. We are about to do a Launch Week so won't be able to test/merge this until August, but this is definitely something we want to support

[dabarrell]

@tartard I was just looking at making a very similar change when I found this PR. Would you be able to expand it to also add the headers to instantiation of the PostgrestClient, SupabaseStorageClient and SupabaseQueryBuilder? These are the other three places headers are used but the settings.headers aren't actually passed in.

If you're not able to make that change let me know and I'll open another PR.

Related to #166

[tartard]

@dabarrell I anticipated this need but it wasn't in my use case, and less easy to implement so I didn't implement it.
When I was thinking about it I was wondering if every client should receive only their expected headers or not. For example, should Postgrest client also receive the X-JWT-AUD header which is intended only to Gotrue client ? I think that filtering would be nicer, but it would also be more development and maintenance work so maybe it is not worth.

But currently I don't have time to work on this, so if you have an idea of how to implement it, yes feel free to open another PR.

[soedirgo]

Thanks for the PR @tartard!

@dabarrell if you'd like to open another PR for the other components, that'd be cool - then we can close #166.

[kiwicopple]

🎉 This PR is included in version 1.22.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀