ui-router / ui-sref, inherited parameters?

Question

I have a couple of parameters that are fundamental and often present in my application.

Simplified exemple of url in the router definition:

url:'/settings/:id'
url:'/profile/:id'
url:'/account/:id'

Do I need to pass this :id parameter on every state.go() or ui-sref?

Example:

ui-sref="settings({id:vm.id})"
ui-sref="profile({id:vm.id})"
ui-sref="account({id:vm.id})"

I would be much simpler if there were a way to copy the named url parameters and specify a specific parameter if I would like to replace it or omit it.

Example:

ui-sref="account"

And if and only if I would like to overwrite it:

ui-sref="account({id:vm.anotherId})"

According to the API inherit is the default behaviour: "inherit Boolean (default true), If true will inherit url parameters from current url." https://github.com/angular-ui/ui-router/wiki/Quick-Reference#stategoto--toparams--options

And this applys to ui-sref also according to: "There is no functional difference between ui-sref and $state.go. See the doc" Difference between ui-sref and $state.go in AngularJS UI-Router

This seems trivial, or I misunderstand something :-( I have tried playing around with nested states, but the real application has not the nested states carasteristics.

I don't really see the point. Why would you want to go from the account 1234 to the profile 1234? account and profile are two completely separate resources, aren't they? If they're two separate parts of the same resource, you'd better use URLs like /foos/:id/profile, /foos/:id/account, and you would then be able to use a parent foo state, and use sibling paths: ^.profile, ^.account. — JB Nizet
– JB Nizet, Commented Dec 29, 2016 at 23:03

Dave · Accepted Answer · 2017-02-22 18:15:30Z

2

I think you need to invert the order of your url, changing it to something like this:

url: user/:id/settings
url: user/:id/profile
url: user/:id/account

It makes more sense this way anyways, you're not looking up the id of a setting, you're looking up the settings of a user/application/website/etc with an id of :id. You can just make the parent state user be abstract and have one of the child states be the default state that navigates to user/:id. That way, the id will be inherited, but you can transition simply by saying ui-sref="^.account" (a relative state transition).

edited Feb 22, 2017 at 18:15

Dave

6,6924 gold badges32 silver badges37 bronze badges

answered Dec 29, 2016 at 23:02

Aaron Pool

4892 silver badges6 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

ui-router / ui-sref, inherited parameters?

1 Answer 1

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Linked

Related