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
I recently encountered an issue while using useFetch where I needed to prevent caching in a request. Unfortunately, it took me several hours of research to discover that a cache option exists for useFetch since it wasn't explicitly mentioned in the documentation. As a beginner, this was quite challenging and led to some frustration.
I believe adding a cache option to the documentation would greatly benefit users like myself. Clear documentation plays a crucial role in making tools accessible, especially for those who are just starting. By explicitly mentioning the cache option and providing usage examples, beginners would be able to leverage this functionality more efficiently, saving time and effort.
I recently encountered an issue while using useFetch where I needed to prevent caching in a request. Unfortunately, it took me several hours of research to discover that a cache option exists for useFetch since it wasn't explicitly mentioned in the documentation. As a beginner, this was quite challenging and led to some frustration.
I believe adding a cache option to the documentation would greatly benefit users like myself. Clear documentation plays a crucial role in making tools accessible, especially for those who are just starting. By explicitly mentioning the cache option and providing usage examples, beginners would be able to leverage this functionality more efficiently, saving time and effort.
Example:
The text was updated successfully, but these errors were encountered: