feature requests about ui-router

[timkindberg]

HI @ludinov thank you for the feedback. This project is still in early alpha, though the sample app seems to work very well, the API is still may change quite a bit. Would you please write each of your requests as a separate issue and label them with the 'feature' label? This will make it easier to have a discussion on each one. I'll close this one.

[ksperling]

@ludinov Item 1 should already work in the API as implemented now (you just use .state(), not .branch())

I wasn't quite sure what the purpose of reloadOnSearch is exactly, i.e. how you would use it in an app. States can reference named search parameters in addition to parameters embedded in the URL path, so if any of those change, views will be reloaded as appropriate.

For example you can use url: '/user/:id/comments?commentId'and as far as $state is concerned, the state has two parameters 'id' and 'commentId' and reloading etc behaviour is exactly the same for both.

1. sounds interesting, can you please open a separate issue
2. I would just wrap each application module in a function scope, then you can define your resolve functions in there and reference from multiple states without polluting the global namespace.

[ludinov]

Thanks a lot for your reply.
I will separate the issues, but I cannot label them.

[timkindberg]

Ah yes I'll label them. Thank you.

On Feb 16, 2013, at 6:15 PM, ludinov [email protected] wrote:

Thanks a lot for your reply.
I will separate the issues, but I cannot label them.

—
Reply to this email directly or view it on
GitHubhttps://github.com/angular-ui/router/issues/20#issuecomment-13676809.