Skip to content

Consider using a named ui-view #446

@sgimeno

Description

@sgimeno

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 unamed ui-view. Wouldn't be nice to be able to embed ng-admin views in a separated and named ui-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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions