@jasonbosco As discussed, the caching logic in typesense-js is deeply embedded and closely tied to the configuration parameters. Currently, when the configuration is refreshed or updated, the existing cache is abandoned. This results in additional Typesense API calls, especially when switching between multiple configurations.
It would be really useful to have an option to persist the cache across configuration updates to reduce redundant calls and improve performance.
@jasonbosco As discussed, the caching logic in typesense-js is deeply embedded and closely tied to the configuration parameters. Currently, when the configuration is refreshed or updated, the existing cache is abandoned. This results in additional Typesense API calls, especially when switching between multiple configurations.
It would be really useful to have an option to persist the cache across configuration updates to reduce redundant calls and improve performance.