mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
b04d4ba9ef
It's possible to declare multiple inputs for a directive/component which all map to the same property name. This is usually done in error, as only one of any bindings to the property will "win". In the template type-checker, an error was previously being raised as a result of this ambiguity. Specifically, a type constructor was produced which required a binding for each field, but only one of the fields had a value via the binding. TypeScript would (rightfully) error on missing values for the remaining fields. This ultimately was happening when the code which generated the default values for "unset" inputs belonging to directives or pipes used the final mapping from properties to fields as a source for field names. Instead, this commit uses the original list of fields to generate unset input values, which correctly provides values for fields which shared a property name but didn't receive the final binding. PR Close #34649 |
||
|---|---|---|
| .. | ||
| fake_core | ||
| BUILD.bazel | ||
| component_indexing_spec.ts | ||
| env.ts | ||
| incremental_error_spec.ts | ||
| incremental_spec.ts | ||
| modulewithproviders_spec.ts | ||
| monorepo_spec.ts | ||
| ngtsc_spec.ts | ||
| scope_spec.ts | ||
| sourcemap_utils.ts | ||
| template_mapping_spec.ts | ||
| template_typecheck_spec.ts | ||