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
I’m working on using typesense-js in a Nuxt application, and I have the goal to manage access to my data by rotating and scoping API-keys through my backend with a fixed ttl. But I'm looking for a way to easily capture any old keys and refreshing them by looking for 401-exceptions through the API. Since you’re using axios I assumed I could use Axios interceptors in a way, but looking through the code i cant seem to find a way to do that. Am I missing something, or is there actually no way to pass interceptors down to the Axios client inside Typesense.Client?
Expected Behavior
A way to pass Axios Interceptors through the Typesense Client.
Actual Behavior
There seem to be no way to pass down Axios Interceptors through the Typesense Client.
The text was updated successfully, but these errors were encountered:
I've tried this, but from what I've read, I don't think global interceptors are automatically copied over when a new Axios-instance is created. I can't seem to get them registered within the TypeSense Axios-instance at least.
Description
I’m working on using typesense-js in a Nuxt application, and I have the goal to manage access to my data by rotating and scoping API-keys through my backend with a fixed ttl. But I'm looking for a way to easily capture any old keys and refreshing them by looking for 401-exceptions through the API. Since you’re using axios I assumed I could use Axios interceptors in a way, but looking through the code i cant seem to find a way to do that. Am I missing something, or is there actually no way to pass interceptors down to the Axios client inside Typesense.Client?
Expected Behavior
A way to pass Axios Interceptors through the Typesense Client.
Actual Behavior
There seem to be no way to pass down Axios Interceptors through the Typesense Client.
The text was updated successfully, but these errors were encountered: