Closed valorkin closed 11 years ago
I think we'll have to make this an option, based on the discussion in #24.
The name of the task target (app
in my examples) should made your module name. If not, you can override the output module name via the module
option.
This way, the templates are automatically added to your existing module by simply including the compiled templates.
If you would like to create a stand-alone module that your module would depend on instead, then this would be the use-case for a standalone option.
@valorkin Did you decide if this warranted a feature, or were you using it differently than anticipated (i.e. where the generated file adds to an existing module, rather than making a standalone one)?
@valorkin I never heard back on if this was user error or an actual requirement, so I closed until I hear otherwise...
Fix for 'No module' error by adding empty requirement [] in angular.module('someModuleName', []) definition