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
Considering hooks can't be used conditionally, parsing through a large list of domains (or addresses) to fetch their counterpart will lead to multiple re-fetch of the same addresses/domains. Currently, this could be circumvented by not using the hook and instead using the vanilla implementation along with a cache.
Proposed Solution
Add a cache state to the hooks, preserving the truthiness (official latest current value) while reducing stress on the router for any doubles.
Implementation
Adding a domain cache state to the hook.
Verifying the cache before fetching the data.
Returning the cache instead of newly fetched data.
Updating the cache with the result whenever a domain/address is fetched.
If you think this would be a good addition , you may assign it to me. I can work on it.
The text was updated successfully, but these errors were encountered:
Problem
Considering hooks can't be used conditionally, parsing through a large list of domains (or addresses) to fetch their counterpart will lead to multiple re-fetch of the same addresses/domains. Currently, this could be circumvented by not using the hook and instead using the vanilla implementation along with a cache.
Proposed Solution
Add a cache state to the hooks, preserving the truthiness (official latest current value) while reducing stress on the router for any doubles.
Implementation
If you think this would be a good addition , you may assign it to me. I can work on it.
The text was updated successfully, but these errors were encountered: