Refreshing in Nested Route redirects to closest parent with non-dynamic model?

I have a route setup like this.

this.resource(tier1) (dynamic_segment)
             this.resource (tier2-Resource) (dynamic_segment)

When refreshing from a route (ex-tier2-child) within the 2nd tier resource, without a dynamic segment, everything works as expected. However when refreshing from a route (ex. refreshing from tier-3 child 1, or child2) within the 3d tier resource which does have a dynamic segment, then ember automatically redirects me to the route within the 2nd nested resource (tier-2 Child) . I am very curious as to how this behaviour might be occurring in the background and how to handle such a case where the user may wish to refresh from a roue with a dynamic segment when the segment is dynamically determined. Is it still just an implementation in the model hook? If handled properly in the model hook will the refresh stop redirecting and will the application refresh into the current nested resource?

Is there more to this?

Yea sorry i accidentally hit enter :smiley:

Very nested question :wink: could you break the usecase down a bit more? It’s difficult to follow.

1 Like

Thank you for updating the description. Its still like trying to understand recursion.

Is there any chance you could replicate this in JSBin?

will do :slight_smile: I won’t get to it till tomorrow probably though. Thanks for your patience

No problem, I look forward to seeing the JSBin.