mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
3e0e0b42fa
This commit captures the metadata on whether an input is signal based or not, in the `.d.ts` of directives and components. This exposes this information to consumers of the directives. This is needed because libraries may use signal inputs, and we need to know whether bound inputs to this library are signal-based or not- so that we can generate proper type-checking code (account for `InputSignal` or not). Additionally, this commit introduces a new structure for the partial compilation output of directive inputs. With the current emit, inputs are captured in a data structure that is equivalent to the internal data structure passed to `defineDirective` (the full compilation output). This worked fine as we only captured a few strings, but in ends up being a bad practice because partial compilation output should NOT capture internal data structures that might be specific to a certian Angular core version. Instead, we introduce a new "future proof" structure that: - can hold additional metadata in backwards-compatible ways, like `isSignal` or `isRequired`. - can be parsed trivially using the `AstHost` for the linker, instead of having to unwrap/parse an array structure. The new structure is only emitted when we discover that some inputs are signal based (or ultimately end up configuring input flags). This is done for backwards compatibility, so that libraries without signal inputs remain compatible with older linker versions. In the future, this might be the only emit. Compliance tests for this follow in future commits, when the linker portion is also in place. This commit specialices on the code generation. With the linker, and compliance test infrastructure fixed (that is broken right now), we can test the full integration. PR Close #53521 |
||
|---|---|---|
| .. | ||
| babel | ||
| src | ||
| test | ||
| BUILD.bazel | ||
| index.ts | ||
| README.md | ||
Angular Linker
This package contains a FileLinker and supporting code to be able to "link" partial declarations of components, directives, etc in libraries to produce the full definitions.
The partial declaration format allows library packages to be published to npm without exposing the underlying Ivy instructions.
The tooling here allows application build tools (e.g. CLI) to produce fully compiled components, directives, etc at the point when the application is bundled.
These linked files can be cached outside node_modules so it does not suffer from problems of mutating packages in node_modules.
Generally this tooling will be wrapped in a transpiler specific plugin, such as the provided Babel plugin.
Unit Testing
The unit tests are built and run using Bazel:
yarn bazel test //packages/compiler-cli/linker/test