You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which scope/s are relevant/related to the feature request?
Don't known / other
Information
Currently the tRPC client does not allow you to pass in custom headers or a custom fetch function to support authentication of the request through e.g. an JWT
Describe any alternatives/workarounds you're currently using
Don’t use auth 😔
I would be willing to submit a PR to fix this issue
Yes
No
The text was updated successfully, but these errors were encountered:
A tRPCHeaders signal is exposed to set/get the headers added
to each tRPC call. This allows us to, e.g. add an authorization
header that we can then use to create protected procedures that
can only be executed when the user is authorized.
closes#394
Which scope/s are relevant/related to the feature request?
Don't known / other
Information
Currently the tRPC client does not allow you to pass in custom headers or a custom fetch function to support authentication of the request through e.g. an JWT
Describe any alternatives/workarounds you're currently using
Don’t use auth 😔
I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: