-
Notifications
You must be signed in to change notification settings - Fork 26
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
IMPORTANT: Need to pass BOTH apikey and Authorization headers! #29
Comments
Thanks for opening your first issue here! 🎉 |
There is the |
@craigpastro I created a separate issue (#32) which I think addresses your comment. Being able to independently set the Authorization and apiKey headers would be useful for Row Level Security purposes. |
@zoogeny Yeah, that is perfect. Thanks for that 🙌 |
hey @craigpastro I just I created a PR #41 to help fix this issue =) |
Just wasted approx 5 hours when I realized you need to pass both an
apikey
ANDAuthorization
key when initializing the client:IMO opinion this should anyway become a single field call 'key' or something, and then within the library itself it is applied to
Hoping this helps anyone who probably otherwise assumed (like I did) that this library was broken!
Please update the README to reflect this information!
The text was updated successfully, but these errors were encountered: