Due to a recent react-router-specific upgrade #171 , some nested components down the routes can't perform automatic data revalidation.
- In some components, we do it manually using the
useRevalidator hook in case of an HTTP request. Ideally, data should be revalidated automatically making use of the router's action APIs. Consider accomplishing this.
- Some components may not explicitly handle data revalidation in response to user interaction. For example, in the
VotingPeriod component data mutation (e.g. castVote() ) is being triggered outside the app. Data fetching is happening in Router's loader on the corresponding route during the page load only.
- Article (route)
|__ArbitrationDetails
|__VotingPeriod
In such a case, we may need to perform the data revalidation for a route manually
Due to a recent react-router-specific upgrade #171 , some nested components down the routes can't perform automatic data revalidation.
useRevalidatorhook in case of an HTTP request. Ideally, data should be revalidated automatically making use of the router's action APIs. Consider accomplishing this.VotingPeriodcomponent data mutation (e.g.castVote()) is being triggered outside the app. Data fetching is happening in Router's loader on the corresponding route during the page load only.In such a case, we may need to perform the data revalidation for a route manually