3 ms·
Isn't that only for one case of errors though (server not matching expected response)? One solution I thought was clever, was a friend's single-page app would
by c-hendricks 3y ago
Isn't that only for one case of errors though (server not matching expected response)?
One solution I thought was clever, was a friend's single-page app would hard-reload on navigation, if there was an update to the assets. Not sure how feasible that would be for schema errors though.
- yencabulator 3y agoBetween that and catching 400 Bad Requests coming back from the server, you're pretty much catching any communication errors resulting from version skew. SvelteKit can poll to check server version and refresh, both on timer and if assets are 404. But as you implied, that doesn't help with API evolution and e.g. users interacting with a form (apart from increasing the likelihood the page will refresh soonish due to navigation).