Fix fallback interval not causing new visits to be loaded #528
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 fallback interval was being tracked in a ref which was updated as a side effect. Since refs do not cause re-renders, the visits for the fallback interval were never loaded.
This PR changes the logic to update a piece of local state instead, which causes a re-render and makes the new visits to be loaded.
Updating local state as a side effect is not a great solution, but this component and how we handle the visits store needs a deeper refactoring to be able to solve this. This is a simple solution for now.
Closes #504