jonataslaw
Caching data from api with Getconnect
Feature Request: Caching Data with GetConnect
Problem: I frequently encounter performance issues when fetching data from the API, and it would be highly beneficial to have a caching mechanism to enhance the overall performance of the application.
Solution:
I propose the implementation of a caching feature in the GetConnect package to allow for the local caching of API responses. This would significantly improve the app's responsiveness by reducing the need to fetch the same data repeatedly from the remote server.
Expected Behavior:
Upon making a request to the API using GetConnect, the response should be cached locally. Subsequent requests for the same data should be served from the cache, provided that the cached data has not expired.
Additional Information:
Having built-in support for caching within GetConnect would streamline the process for developers and provide a standardized solution for efficient data retrieval and caching.
Alternatives Considered:
One alternative could be implementing a custom caching mechanism, but having native support for caching in GetConnect would offer a more straightforward and consistent approach.
Screenshots/Code Snippets (if applicable): No applicable screenshots or code snippets at the moment.
