reload option in transitionTo reloads all states in a hierarchy. Unable to reload just the current nested state.

[gfreeau]

When using the reload option in state.transitionTo on a nested state, all of its parents are also reloaded. You should be able to reload only the current state.

My use case is a nested state with params. In some cases I have the same state and params and I simply wish to reload it (to refresh data from the server), however using the reload option also reloads it's parents, which resets templates and directives in parent states.

One workaround I found is to have some kind of random param in the nested state which is changed every time you wish to reload/refresh the current state. UI-Router seems to handle the case fine when a state has unique params every time, it just cannot reload a state with the exact same params since it believes there is no work to do.

Here is what happens:

• Nested state, no changes to params = UI router does nothing, since it assumes it is already on the correct state
• Nested state, with an additional unique param assigned to a random value to uniquely identify every transitionTo call = works correctly, able to "refresh" nested states without reloading parents
• using the reload option, refreshes the nested state correctly but also reloads all parents

I can setup a plunk, I just wanted to see if this is worthwhile first.

[ProLoser]

What if reload to a string name of the state at which you want to reload?

state1.state2.state3

reload: false // default behavior
reload: true // full tree reload
reload: 'state3' // only last child is reloaded
reload: 'state2' // state2 and deeper (state3) are reloaded

Alternatively, is this really an issue about transitioning? Or do you just want to reload a state you're already sitting in? In which case, should we be looking at a reload() method directly and it's behavior (which of course could possibly be a reflection of the two truthy versions above so as to allow code reuse).

[gfreeau]

@ProLoser, It's not directly related to transitioning, it'a about reloading the controller/resolves for a state with the goal of refreshing data in the current state.

However it would be solved if we could reload selected states or a partial hierarchy of states, which would in turn reload the controllers/resolves.

[gfreeau]

Just wanted to share my work-around for reloading partial states. First of all don't use the reload option at all. Create a parameter for the state such as

params: {
    uniqueRequestCacheBuster: null
}

Then if you ever need to reload the current state without parents using the same parameters, you can do it with transitionTo

var params = angular.copy($stateParams);
params.uniqueRequestCacheBuster = Math.random();

$state.transitionTo($state.current, params);

The cache buster parameter will not show up in the URL.

UI-Router natively handles reloading only partial hierarchies of states when url parameters are changed. if you use the reload option, it will reload all parents as well.

This works thanks to @christopherthielen work on params.

[ProLoser]

I would still prefer to see reload take a string value.

[gfreeau]

That is a better option longer term.

[christopherthielen]

Seem reasonable

[Astray-git]

I have a similar problem with the reload. I use resolves to update data in my state's controller.(when it's an active state)
I use the params work-around above, it does reload the resolves, but doesn't reinitialize the controller, the injected resolve is not updated. I also tried transition with options
{ reload: true, inherit: false, notify: true } which didn't work neither.

[deanapeterson]

The ability to set the descendant depth of the reload is an excellent idea.

[oriweingart]

We implemented this feature for a private project.
PR was created: #1795
Welcome to try it..

[christopherthielen]

I think this makes sense and is a good idea. I'd like to omit the second reloadState parameter, and overload the existing reload parameter.

• { reload: true }// reloads all,
• { reload: 'foo.bar' } // reloads top.bar, and any children
• { reload: stateObj } // reloads state found in stateObj, and any children

Squash your commits and set your commit message to match the contributor guidelines. If @nateabele concurs, I think we'll merge this in.

[oriweingart]

Created a new PR according to your comments: #1809

[nateabele]

Fixed in #1809.

[shyamal890]

+1 Was looking this since long back. Thank you.

[DumboJet]

Can reload accept a list of states to reload?
Or it is too much to ask?

{ reload: ['foo.bar','foo.bar.car.jar'] }

[ProLoser]

@DumboJet that doesn't make any sense since reloading a parent state reloads the descendents