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
Our current codebase doesn't really handle loading and error states for all api requests, it also makes redundant/unnecessary api calls when switching between views or tabs every time leading to a less optimal user experience.
Acceptance Criteria:
Each composable for making api requests should probably return loading and error states to be used in the ui to properly show the state.
Eliminate random setTimeout calls that predict when a response will be received
Cache api requests to avoid redundant requests
Using something like https://github.com/TanStack/query/ could also avoid the need for over-reliance on the pinia store and handle our requests in a better way with built in polling/refetchQueries, etc.. instead of having to make follow up api requests manually after adding something to update the UI
Alternatives
Vanilla Implementation
Using tanstack/query or similar implementations
Contribution
No response
Have you searched for similar issues before submitting this one?
Yes, I have searched for similar issues
The text was updated successfully, but these errors were encountered:
khaledosman
changed the title
[FEATURE]: Cache api requests and properly handling loading and error states for all api requests
[FEATURE]: Cache api requests and properly handle loading and error states for all api requests
Feb 12, 2025
Motivation
Our current codebase doesn't really handle loading and error states for all api requests, it also makes redundant/unnecessary api calls when switching between views or tabs every time leading to a less optimal user experience.
Acceptance Criteria:
setTimeout
calls that predict when a response will be receivedAlternatives
Vanilla Implementation
Using tanstack/query or similar implementations
Contribution
No response
Have you searched for similar issues before submitting this one?
The text was updated successfully, but these errors were encountered: