I finally got rid of it; kiwiupower's answer was correct, as Ember looks for template files in folders and subfolders as specified; the problem was caused by the yeomen that I use for development; in the grunt file, the default setting searches for Ember templates through only one level of folders;
to make yoman able to look even deeper in the template folder structure, I made the following changes:
1 to the view task for loading in a stream:
emberTemplates: { files: '<%= yeoman.app %>/templates/**/**/*.hbs', tasks: ['emberTemplates', 'livereload'] },
I added "** /" so that the task also tracks the second level of subfolders in the template directory
2 in the Ember templates task:
emberTemplates: { options: { templateName: function (sourceFile) { var templatePath = yeomanConfig.app + '/templates/'; return sourceFile.replace(templatePath, ''); } }, dist: { files: { '.tmp/scripts/compiled-templates.js': '<%= yeoman.app %>/templates/{,*/}{,*/}*.hbs' } } }
I added "{, /}" to the dist.files object; If you need a yoman to view / compile the third level of subfolders or more, you need to change these two tasks by adding more "* /" and "{, * /}"
source share