Sticky states get reloaded unexpectedly

[arthastft]

Hello christopher,
Say I have following states structure:

parent1: { sticky: true }
parent1.child1: { sticky: true }
parent1.child2: { sticky: false }

parent2: { sticky: false }
parent2.child1: { sticky: false }

When I do: parent1.child1 => parent2.child1 => parent1.child1, it works normally.
But when: parent1.child1 => parent2.child1 => parent1.child2 => parent1.child1, parent1.child1 gets reloaded.

[christopherthielen]

@arthastft could you put this in a plunk for me? I agree that behavior seems wrong

[arthastft]

Of course, here: http://plnkr.co/edit/n4UEJ4qATykdUxEoez3v?p=preview.
I've found out a workaround that if I set all the states parallel to parent1.child1 to sticky, the problem goes away. Not ideal though.

[christopherthielen]

Yes, I see how this is happening now.
https://github.com/christopherthielen/ui-router-extras/blob/master/src/stickyStateProvider.js#L180

"Deepest reactivate" is intended for when you directly reactivate a sticky state (without DSR), it should exit the children of that state. For example, from parent1.child1 to parent1 should exit parent1.child. Your use case causes deepestReactivate to be populated with your parent1 state, but then the logic for the use case above kicks in and removes parent1.child form the inactives list. This will take a little bit of rework.

[arthastft]

Hi christopher,
I'm afraid that the problem is still here.
I just updated the plunker to reference 0.0.13: http://plnkr.co/edit/n4UEJ4qATykdUxEoez3v?p=preview