I have a route (/search) that gets updated when it's query params are updated. There is a top level component with a search bar that passes it's input into the nested route and updates the queryparam to trigger a change.
On an API error rendered into the nested outlet, queryParamsDidChange is no longer triggered on the route.
This leads me to believe there is a substate route or something inherently built in that I'm missing. What is the best way to handle this situation so that I can update the model and trigger a refresh on query param change?
Aucun commentaire:
Enregistrer un commentaire