$state.go reload defined as reload lost control of cache.

[ccsldya]

This is a:

• [x] Bug Report

My version of UI-Router is: (version)

v1.0.5

Bug Report

Current Behavior:

1. I have tree, and depend on the treenode type property , it will direct to diffect view;
2. I have two same "type" treenode name is node1 and node2 , both of them will direct to "parent.children";
3. when I already in node1 with state "parent.children", click node2 and do $state.go('parent.children', {}, {reload : 'parent.children'});
4. It not refreshed; I need the "children" state refresh only; I know if the "{reload : 'parent.children'” , means it will refresh and redirect to the sub state "parent.children'" only, "parent" will not refresh; but here I lost control of "reload:true" which should meaning "cache", if I want to force refresh "children"

Expected Behavior:

We need a params that can force reload the children view only . reload =true or false is means if we need to cache the view, current design to add "object " on "reload" to determine if load the parent or children is not good. this design confilct with the cache meaning.

In a word, reload only children state and reload if need cache should be different params;

Link to Plunker that reproduces the issue:

http://bit.ly/UIR-Plunk

Feature Request

(feature request here)

General Query

Please direct general implementation questions to StackOverflow: http://stackoverflow.com/questions/ask?tags=angularjs,angular-ui-router

Please review the Sample Application which highlights common approaches: https://github.com/ui-router/sample-app-ng1

• [ ] I have already asked my question on StackOverflow and nobody could answer the question

• [ ] I have already reviewed the sample application for examples of common approaches

• [ ] I believe my question can only be answered by the UI-Router maintainers

(general query here)

[ccsldya]

anyone can help me..?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

This does not mean that the issue is invalid. Valid issues may be reopened.

Thank you for your contributions.