Pawel Kozlowski d7b9345b6d feat(compiler): detect dangling property bindings ... BREAKING CHANGE: compiler will throw on binding to non-existing properties. Till now it was possible to have a binding to a non-existing property, ex.: `<div [foo]="exp">`. From now on this is compilation error - any property binding needs to have at least one associated property: eaither on an HTML element or on any directive associated with a given element (directives' properites need to be declared using the `properties` field in the `@Directive` / `@Component` annotation). Closes #2598		2015-06-20 08:06:07 +02:00
..
compile_control.ts	chore: kill ListWrapper.create() and .push().	2015-06-17 16:21:55 -07:00
compile_element.ts	feat: remove MapWrapper.create()/get()/set().	2015-06-18 14:55:12 -07:00
compile_pipeline.ts	chore: kill ListWrapper.create() and .push().	2015-06-17 16:21:55 -07:00
compile_step.ts	refactor(render): ts’ify render api	2015-05-19 15:12:59 -07:00
compile_step_factory.ts	style(render): idiomatic TS	2015-06-15 18:53:47 +02:00
compiler.ts	feat(View): add support for styleUrls and styles	2015-06-15 19:35:16 +02:00
directive_parser.ts	feat(compiler): detect dangling property bindings	2015-06-20 08:06:07 +02:00
property_binding_parser.ts	feat: remove MapWrapper.create()/get()/set().	2015-06-18 14:55:12 -07:00
selector.ts	feat: remove MapWrapper.create()/get()/set().	2015-06-18 14:55:12 -07:00
template_loader.ts	feat: remove MapWrapper.create()/get()/set().	2015-06-18 14:55:12 -07:00
text_interpolation_parser.ts	fix(compiler): make text interpolation more robust	2015-06-18 15:45:00 -07:00
view_splitter.ts	feat: remove MapWrapper.create()/get()/set().	2015-06-18 14:55:12 -07:00