-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
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
how to use @StateConfig with ui-router multiple view sections #117
Comments
@tolemac probably I wrote it wrong. I was talking about multiple root views at the same level with its subviews |
I think you have to do nothing new, Have you try this?
|
Yeah I should add a feature to route a component to a named view. Right now that's not supported I don't think. |
I think ng-forward should wait for ngComponentRouter, at the moment I wouldn't loss time with ui-router. IMHO. |
Well ui-router has been the leading router. It will support Angular 2 at some point. Right now it's the best we got. We plan to support both it and the new router. |
So I looked around and I could not find any code samples defining abstract states without a url or component defined. From what I could see if you try to define such states you get the following error :
I suppose I'm doing it wrong somehow. It seems all samples I can find already define top level routes and import the required components for them. How would one do it if you wanted to only define the layout states without knowing what components you will need or the url for them?
|
Is there such ability? no info about it in the docs and examples
The text was updated successfully, but these errors were encountered: