(Dialog) 404 returned for messageBox dialog template if module specifies only 'ui.bootstrap.dialog' instead of 'ui.bootstrap' as dependency

[aravinda0]

It could be that I'm missing something obvious, so just go ahead and close this if this is an oversight.

In this plnkr, http://plnkr.co/edit/aix6PZ?p=preview, I have only 'ui.bootstrap.dialog' specified as a requirement. This causes a 404 on clicking the messageBox generating button.

If I change the dependency to 'ui.bootstrap', it works again.

[pkozlowski-opensource]

@ManiacalAce yes, this is how this should behave. We are delivering this library with both templates bundled and not, see https://github.com/angular-ui/bootstrap/tree/gh-pages#build-files for more info. Non-bundled version is for people who want to customize templates.

In the version with bundled templates we are pre-caching them creating a module for each template and putting template's content into $templateCache like this:
https://github.com/angular-ui/bootstrap/blob/gh-pages/ui-bootstrap-tpls-0.2.0.js#L1745

So if you want to use several directives from this repo with default templates you should just add dependency on ui.bootstrap. If you want to have fine-grained control on module dependencies and use bundled templates you should add a dependency on both JavaScript module and template module, ex.:

angular.module('plunker', ['ui.bootstrap.dialog', 'template/dialog/message.html']);

and this makes plunker work: http://plnkr.co/edit/Gq3TBA?p=preview

In practice such fine-grained listing of dependencies can be painful but be aware that you can create a custom build including only directives you are planning to use. Just click on the Create a Build button on:
http://angular-ui.github.com/bootstrap/

I know that this all makes many options and can be a bit difficult to choose a correct one but we want to give users flexibility in providing they own templates for the directives from this repo.

[aravinda0]

Thanks a lot for that explanation. My doubts are cleared.