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
Currently the AvResourceSelect components use axios based data-fetching functions and a decent amount of manual logic to control when and how this occurs.
Desired Behavior
These components should utilize react-query to take advantage of it's built-in caching capabilities among other features.
Suggested Solution
Specifically i want to be able to pre-cache the response data for an AvResourceSelect component. Consider this common use case: we have already fetched user organizations on a previous page and when we go to a new form and render an AvOrganizationSelect we are forced to re-fetch this data.
Who does this impact? Who is this for?
All users and platform maintainers benefit from reducing unnecessary api calls
Describe alternatives you've considered
There are lots of other http caching solutions but react-query is commonly used in other Availity components so for consistency this seems the obvious choice to me.
Additional context
None at the moment. If this work is assigned internally will update this ticket with progress.
The text was updated successfully, but these errors were encountered:
🚀 Feature request
Current Behavior
Currently the AvResourceSelect components use axios based data-fetching functions and a decent amount of manual logic to control when and how this occurs.
Desired Behavior
These components should utilize react-query to take advantage of it's built-in caching capabilities among other features.
Suggested Solution
Specifically i want to be able to pre-cache the response data for an AvResourceSelect component. Consider this common use case: we have already fetched user organizations on a previous page and when we go to a new form and render an AvOrganizationSelect we are forced to re-fetch this data.
Who does this impact? Who is this for?
All users and platform maintainers benefit from reducing unnecessary api calls
Describe alternatives you've considered
There are lots of other http caching solutions but react-query is commonly used in other Availity components so for consistency this seems the obvious choice to me.
Additional context
None at the moment. If this work is assigned internally will update this ticket with progress.
The text was updated successfully, but these errors were encountered: