From 3ee744cc63a24b127d6a5f632934bb6ed2de275a Mon Sep 17 00:00:00 2001 From: Jeff Cross Date: Wed, 24 Jul 2013 10:17:24 -0700 Subject: fix(re-bootstrap): Throw an error when bootstrapping a bootstrapped element. Nothing would prevent a user from accidentally calling angular.bootstrap on an element that had already been bootstrapped. If this was done, odd behavior could manifest in an application, causing different scopes to update the same DOM, and causing debugger confusion. This fix adds a check inside of angular.bootstrap to check if the passed-in element already has an injector, and if so, will throw an error. --- docs/content/error/ng/btstrpd.ngdoc | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 docs/content/error/ng/btstrpd.ngdoc (limited to 'docs/content/error') diff --git a/docs/content/error/ng/btstrpd.ngdoc b/docs/content/error/ng/btstrpd.ngdoc new file mode 100644 index 00000000..401e2767 --- /dev/null +++ b/docs/content/error/ng/btstrpd.ngdoc @@ -0,0 +1,29 @@ +@ngdoc error +@name ng:btstrpd +@fullName App Already Bootstrapped with this Element +@description + +Occurs when calling angular.bootstrap on an element that has already been bootstrapped. + +This usually happens when you accidentally use both `ng-app` and `angular.bootstrap` to bootstrap an application. + +``` + +... + + + + +``` + +Note that for bootrapping purposes, the `` element is the same as `document`, so the following will also throw an error. +``` + +... + + +``` -- cgit v1.2.3