-
Notifications
You must be signed in to change notification settings - Fork 723
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
Consider using a named ui-view #446
Comments
Hi Sergio, and thanks for your feedback. Yes, we are aware of this issue, and using a not-main view is indeed the solution. The only problem is that it would break existing applications. I guess the best way (and the only BC way) would be to add a second parameter to the @jpetitcolas any feedback on this? |
Related to #335 |
Passed parameter is already called Moreover, isn't the name |
The I'm +1 with your suggestion to add a parameter to the |
+1 |
+1 |
No workaround for now, I think. |
+1 |
1 similar comment
+1 |
+100 |
It should be solved with last master version, which breaks backward compatibility to use a named view. You now have to name your admin div as:
|
First of all props to all maintainers for the great job on this angular module. I'm already using it in a couple of projects.
When writing a simple Angular web app to display ng-admin views as a "backoffice" for some data source I can't build other angular-ui-router
ui-view
's because ng-admin needs an unamedui-view
. Wouldn't be nice to be able to embed ng-admin views in a separated and namedui-view
? Is there any other approaches I'm missing or is this out of the scope of the project?So far I also found this article which encourages to use named
ui-view
's:http://www.toptal.com/angular-js/top-18-most-common-angularjs-developer-mistakes#common-mistake-5-not-using-named-views-with-ui-router-for-power
The text was updated successfully, but these errors were encountered: