Default behaviour should name the module and $templateCache identifier by the full template path

[javoire]

The default behaviour (as described in #37) seems unintuitive to me. Instead I would propose a behaviour like this:

var angular = require('angular');

require('ui-router');

angular.module('myApp', [
  'ui.router',
  require('./templates/home.html') // the module name would be '/templates/home.html' by default
]).config(function($stateProvider){
  $stateProvider.state('home', {
    url: '/',
    templateUrl: '/templates/home.html' // full path by default
  });
});

The name of the generated module would be the full path to the template instead of just the filename. This is currently achieved with baseDir: "src/js" // optionally specify base directory for filename.

Thoughts?

[ernestoalejo]

Would this solve the issue when the template is next to the file requiring it?, for example:

// Folder /assets/scripts/part1/foo-bar-baz.js
Component.define('fooBarBaz', {
  controller: Ctrl,
  templateUrl: require('./foo.html'),
});

// Folder /assets/scripts/part2/baz-bar-foo.js
Component.define('bazBarFoo', {
  controller: Ctrl,
  templateUrl: require('./foo.html'),
});

These two foo.html are different files in different folders; but one overwrites the other.

[ernestoalejo]

Oops, I tested baseDir incorrectly, it's working now after I changed it. I agree it should be the full path to avoid unexpected consecuences (two templates bundled overwriting one another).