angular/modules/@angular/core/testing
Tobias Bosch 00b726f695 refactor(core): introduce NgModule.schemas
This allows Angular to error on unknown properties,
allowing applications that don’t use custom elements
to get better error reporting.

Part of #10043

BREAKING CHANGE:
- By default, Angular will error during parsing
  on unknown properties,
  even if they are on elements with a `-` in their name
  (aka custom elements). If you application is using
  custom elements, fill the new parameter `@NgModule.schemas`
  with the value `[CUSTOM_ELEMENTS_SCHEMA]`.

  E.g. for bootstrap:
  ```
  bootstrap(MyComponent, {schemas: [CUSTOM_ELEMENTS_SCHEMA]});
  ```
2016-07-26 07:04:36 -07:00
..
async.ts fix: public api surface fixes + stability markers 2016-06-28 07:39:40 -07:00
async_test_completer.ts chore(lint): Added license headers to most TypeScript files 2016-06-23 09:47:54 -07:00
component_fixture.ts fix(testing): ComponentFixture - Avoid extra scheduleMicrotask (#10223) 2016-07-22 16:07:11 -07:00
fake_async.ts fix: public api surface fixes + stability markers 2016-06-28 07:39:40 -07:00
lang_utils.ts chore(lint): Added license headers to most TypeScript files 2016-06-23 09:47:54 -07:00
logger.ts chore(lint): Added license headers to most TypeScript files 2016-06-23 09:47:54 -07:00
mock_animation_player.ts refactor(animations): move MockAnimationPlayer back into core (#9966) 2016-07-11 10:55:47 -07:00
mock_application_ref.ts chore(lint): Added license headers to most TypeScript files 2016-06-23 09:47:54 -07:00
ng_zone_mock.ts chore(lint): Added license headers to most TypeScript files 2016-06-23 09:47:54 -07:00
test_bed.ts refactor(core): introduce NgModule.schemas 2016-07-26 07:04:36 -07:00
test_component_builder.ts refactor(core): change module semantics 2016-07-26 07:04:10 -07:00
testing.ts refactor(core): introduce NgModule.schemas 2016-07-26 07:04:36 -07:00
testing_internal.ts fix(testing): correctly import NgMatchers (#10077) 2016-07-22 09:20:51 -07:00