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
..
browser	refactor(core): introduce NgModule.schemas	2016-07-26 07:04:36 -07:00
dom	fix(testing): correctly import NgMatchers (#10077)	2016-07-22 09:20:51 -07:00
security	feat(security): trust resource URLs as URLs. (#10220)	2016-07-21 17:44:59 -07:00
static_assets	repackaging: all the file moves	2016-05-01 20:51:00 -07:00
web_workers	refactor(core): change module semantics	2016-07-26 07:04:10 -07:00
browser_util_spec.ts	fix(testing): remove deprecated testing APIs (#9923)	2016-07-11 16:04:32 -07:00
testing_public_spec.ts	refactor(core): introduce NgModule.schemas	2016-07-26 07:04:36 -07:00