We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I am using the state params property to define non-url params as such:
$stateProvider .state('site', { abstract: true, // url: '', // try uncommenting this line ---------------------------- template: '<ui-view/>', params: { siteParam: null, }, }) .state('site.home', { url: '/home', templateUrl: 'tpl.html' }) .state('site.page', { url: "/page", templateUrl: 'tpl.html' });
The problem is that the siteParam will only be populated, if the url is defined.
I don't know if this is by design. I can't really tell from reading the doc.
I've done a plunkr to illustrate: http://plnkr.co/edit/o9ZfAAvF1eQBIcVa7BNg
If you uncomment line 14 in script.js, you'll see the siteParam is populated.
This is actually not a big deal for me, since setting:
{ ... abstract: true, url: '', ... }
works fine for my needs.
Thanks,
The text was updated successfully, but these errors were encountered:
verified, thanks for the report
Sorry, something went wrong.
d6d8c33
fix(stateBuilder): fix non-url params on a state without a url.
aa999fb
The parameters are now applied when transitioning to a child state. Closes angular-ui#2025
christopherthielen
No branches or pull requests
Hi,
I am using the state params property to define non-url params as such:
The problem is that the siteParam will only be populated, if the url is defined.
I don't know if this is by design. I can't really tell from reading the doc.
I've done a plunkr to illustrate:
http://plnkr.co/edit/o9ZfAAvF1eQBIcVa7BNg
If you uncomment line 14 in script.js, you'll see the siteParam is populated.
This is actually not a big deal for me, since setting:
works fine for my needs.
Thanks,
The text was updated successfully, but these errors were encountered: