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 develop with React hooks
I used a lot with SWR
I recommend adding the caching properties they implement in inertia calls
At the entrance to a particular page it will be saved in the local cache for reuse
The cache was saved with a key that was the url
Mutations
Cached value can be re-verified manually / automatically at intervals
There will also be re-authentication when entering the tab in the browser and when reconnecting the internet
It can be leveraged much more so that it will be possible to re-authenticate on a group of urls
For example, in updating a user or creating a new user - the index page and all paginate pages be re-validated or remove keys
You can also add a backoffice version so that once a user has managed backend data
The end user will automatically empty the keys associated with the update to receive up-to-date information
Try to think about it
This will give a lot of server resource savings
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Greetings
I develop with React hooks
I used a lot with SWR
I recommend adding the caching properties they implement in inertia calls
At the entrance to a particular page it will be saved in the local cache for reuse
The cache was saved with a key that was the url
Mutations
Cached value can be re-verified manually / automatically at intervals
There will also be re-authentication when entering the tab in the browser and when reconnecting the internet
It can be leveraged much more so that it will be possible to re-authenticate on a group of urls
For example, in updating a user or creating a new user - the index page and all paginate pages be re-validated or remove keys
You can also add a backoffice version so that once a user has managed backend data
The end user will automatically empty the keys associated with the update to receive up-to-date information
Try to think about it
This will give a lot of server resource savings
Beta Was this translation helpful? Give feedback.
All reactions