angular-cn/modules/@angular/core
Victor Berchet e99d721612 feat(compiler): Add a `enableLegacyTemplate` option to support `<template>`
When the `enableLegacyTemplate` is set to `false`, `<template>` tags and the
`template` attribute are no more used to define angular templates but are
treated as regular tag and attribute.

The default value is `true`.

In order to define a template, you have to use the `<ng-template>` tag.

This option applies to your application and all the libraries it uses. That is
you should make sure none of them rely on the legacy way to defined templates
when this option is turned off (`false`).
2017-02-23 20:03:16 -08:00
..
src feat(compiler): Add a `enableLegacyTemplate` option to support `<template>` 2017-02-23 20:03:16 -08:00
test feat(compiler): introduce `<ng-template>`, deprecate `<template>` and `template` attribute 2017-02-23 20:03:16 -08:00
testing perf: distrubute smaller bundled code and include es2015 bundle 2017-02-21 20:48:55 -08:00
.babelrc build: resolve review comments on flat modules PR and fix more bugs (#14660) 2017-02-23 16:39:44 -08:00
.babelrc-testing build: resolve review comments on flat modules PR and fix more bugs (#14660) 2017-02-23 16:39:44 -08:00
index.ts feat(platform-webworker): renderer v2 integration 2017-02-20 16:17:43 -08:00
package.json perf: distrubute smaller bundled code and include es2015 bundle 2017-02-21 20:48:55 -08:00
public_api.ts build: produce metadata bundles for @angular modules (#14509) 2017-02-16 08:15:30 -08:00
tsconfig-build.json fix(tsc-wrapped): use agreed on options names (#14630) 2017-02-22 10:57:01 -08:00
tsconfig-testing.json build: resolve review comments on flat modules PR and fix more bugs (#14660) 2017-02-23 16:39:44 -08:00