@GrandSlam90 wrote:
I have a nested route which doesn't seem to want to update when I save a new record to the model.
If I visit my colleagues/colleague/{id}/vacation route I get a list of models which is correct. To add a vacation, the users clicks a button that does a transitionTo in the controller to the colleague's/colleague/{id}/vacation/request route. This route contains the form and validation logic for a new vacation and is an {{outlet}} of the parent path.
Where things get weird is I can pass validation, save the record to the model, verify its presence on the backend (i.e. it saved successfully) but it doesn't update the current list.
Even if I trigger a transitionTo to go back to the parent route after a successful save the route doesn't refresh so the model doesn't update.
However, if I refresh the browser manually, this performs a fetch (GET) from the backend and the added vacation is there!
What am I missing or have I misunderstood nested routes/outlets?
Posts: 2
Participants: 2
