fix: prevent stale data when using the back button (fixes #12914) #13371
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The browser showed stale data when using the back button after making changes to the database. This happened because the browser's bfcache was restoring the previous state instead of fetching the updated data.
To solve this, I added a router.refresh() after the database update to force the page to reload and reflect the latest state. This is a reliable temporary fix, but I understand that it increases backend calls. I'm planning to improve this further by removing the refresh and implementing a more efficient, reactive solution.
Fixes #12914