mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
2028c3933f
Currently the compiler has three different classes to represent a "call to something": 1. `MethodCall` - `foo.bar()` 2. `SafeMethodCall` - `foo?.bar()`. 3. `FunctionCall` - Any calls that don't fit into the first two classes. E.g. `foo.bar()()`. There are a few problems with this approach: 1. It is inconistent with the TypeScript AST which only has one node: `CallExpression`. 2. It means that we have to maintain more code, because the various parts of the compiler need to know about three node types. 3. It doesn't allow us to easily implement some new JS features like safe calls (e.g. `foo.bar?.())`). These changes rework the compiler so that it produces only one node: `Call`. The new node behaves similarly to the TypeScript `CallExpression` whose `receiver` can be any expression. There was a similar situation in the output AST where we had an `InvokeMethodExpression` and `InvokeFunctionExpression`. I've combined both of them into `InvokeFunctionExpression`. PR Close #42882 |
||
|---|---|---|
| .. | ||
| aot | ||
| expression_parser | ||
| i18n | ||
| ml_parser | ||
| output | ||
| render3 | ||
| schema | ||
| selector | ||
| template_parser | ||
| BUILD.bazel | ||
| compiler_facade_interface_spec.ts | ||
| config_spec.ts | ||
| core_spec.ts | ||
| directive_lifecycle_spec.ts | ||
| directive_normalizer_spec.ts | ||
| directive_resolver_mock_spec.ts | ||
| directive_resolver_spec.ts | ||
| integration_spec.ts | ||
| metadata_resolver_fixture.ts | ||
| metadata_resolver_spec.ts | ||
| ng_module_resolver_mock_spec.ts | ||
| ng_module_resolver_spec.ts | ||
| parse_util_spec.ts | ||
| pipe_resolver_mock_spec.ts | ||
| pipe_resolver_spec.ts | ||
| resource_loader_mock_spec.ts | ||
| runtime_compiler_spec.ts | ||
| shadow_css_spec.ts | ||
| style_url_resolver_spec.ts | ||
| test_bindings.ts | ||
| url_resolver_spec.ts | ||
| util_spec.ts | ||