angular-cn/public/docs/js/latest/api/change_detection/ChangeDetection-class.jade

p.
  <span class="location-badge">exported from <a href="/angular2/change_detection">angular2/change_detection</a></span>
  defined in <a href="https://github.com/angular/angular/tree/master/modules/angular2/src/change_detection/interfaces.js#L34">angular2/src/change_detection/interfaces.js (line 34)</a>

:markdown
  Interface used by Angular to control the change detection strategy for an application.
  
  Angular implements the following change detection strategies by default:
  
  - <a href="angular2/change_detection/DynamicChangeDetection-class"><code>DynamicChangeDetection</code></a>: slower, but does not require `eval()`.
  - <a href="angular2/change_detection/JitChangeDetection-class"><code>JitChangeDetection</code></a>: faster, but requires `eval()`.
  
  In JavaScript, you should always use `JitChangeDetection`, unless you are in an environment that has
  [CSP](https://developer.mozilla.org/en-US/docs/Web/Security/CSP), such as a Chrome Extension.
  
  In Dart, use `DynamicChangeDetection` during development. The Angular transformer generates an analog to the
  `JitChangeDetection` strategy at compile time.
  
  
  See: <a href="angular2/change_detection/DynamicChangeDetection-class"><code>DynamicChangeDetection</code></a>, <a href="angular2/change_detection/JitChangeDetection-class"><code>JitChangeDetection</code></a>
  
  # Example
  ```javascript
  bootstrap(MyApp, [bind(ChangeDetection).toValue(dynamicChangeDetection)]);
  ```
.l-main-section
  h2 Members
  .l-sub-section
    h3 createProtoChangeDetector

    
    pre.prettyprint
      code.
        createProtoChangeDetector(name:string, changeControlStrategy:string=DEFAULT)
    

    :markdown