HI , I've been looking over the code for the new router, coming from a ui-router background. I can see the use of conventions for mapping components to templates and controllers, but it also feels very limiting not to be able to configure these. To support the multiple level folder architecture i override the setTemplateMapping,setComponentFromCtrlMapping and setCtrlNameMapping, after override my url is working on browser but ng-link button or hyperlink is not working. As per my understanding it is issue on ng-link that it's not working when i used the slash on component. Here is my code.
/* Override the $componentLoaderProvider*/
appVar.config([ '$componentLoaderProvider', function ($componentLoaderProvider) {
var DEFAULT_SUFFIX = 'Controller';
HI , I've been looking over the code for the new router, coming from a ui-router background. I can see the use of conventions for mapping components to templates and controllers, but it also feels very limiting not to be able to configure these. To support the multiple level folder architecture i override the setTemplateMapping,setComponentFromCtrlMapping and setCtrlNameMapping, after override my url is working on browser but ng-link button or hyperlink is not working. As per my understanding it is issue on ng-link that it's not working when i used the slash on component. Here is my code.
/* Override the $componentLoaderProvider*/
appVar.config([ '$componentLoaderProvider', function ($componentLoaderProvider) { var DEFAULT_SUFFIX = 'Controller';
/* Controller */
angular.module('app', ['ngNewRouter', 'ngAnimate', 'ngMaterial', 'app.home', 'app.detail']) .controller('AppController', ['$router', AppController]);
AppController.$routeConfig = [ { path: '/', component: 'home/home' }, { path: '/home', component: 'home/home' }, { path: '/detail/:id', component: 'detail/detail' }, { path: '/childDetail/:id', component: 'childDetail/childDetail' } ];