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 |
||
|---|---|---|
| .circleci | ||
| .devcontainer | ||
| .github | ||
| .husky | ||
| .ng-dev | ||
| .vscode | ||
| .yarn | ||
| adev | ||
| aio | ||
| devtools | ||
| docs | ||
| goldens | ||
| integration | ||
| modules | ||
| packages | ||
| scripts | ||
| third_party | ||
| tools | ||
| .bazelignore | ||
| .bazelrc | ||
| .bazelversion | ||
| .clang-format | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmessage | ||
| .mailmap | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierrc | ||
| .pullapprove.yml | ||
| .yarnrc | ||
| angular.json | ||
| browser-providers.conf.d.ts | ||
| browser-providers.conf.js | ||
| BUILD.bazel | ||
| CHANGELOG.md | ||
| CHANGELOG_ARCHIVE.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| gulpfile.js | ||
| karma-js.conf.js | ||
| LICENSE | ||
| package.json | ||
| packages.bzl | ||
| README.md | ||
| renovate.json | ||
| SECURITY.md | ||
| tsconfig-tslint.json | ||
| tslint.json | ||
| WORKSPACE | ||
| yarn.bzl | ||
| yarn.lock | ||
| yarn.lock.readme.md | ||
Angular - The modern web developer's platform
Angular is a development platform for building mobile and desktop web applications
using TypeScript/JavaScript and other languages.
Contributing Guidelines
·
Submit an Issue
·
Blog
Documentation
Get started with Angular, learn the fundamentals and explore advanced topics on our documentation website.
Advanced
Development Setup
Prerequisites
- Install Node.js which includes Node Package Manager
Setting Up a Project
Install the Angular CLI globally:
npm install -g @angular/cli
Create workspace:
ng new [PROJECT NAME]
Run the application:
cd [PROJECT NAME]
ng serve
Angular is cross-platform, fast, scalable, has incredible tooling, and is loved by millions.
Quickstart
Ecosystem
Changelog
Learn about the latest improvements.
Upgrading
Check out our upgrade guide to find out the best way to upgrade your project.
Contributing
Contributing Guidelines
Read through our contributing guidelines to learn about our submission process, coding rules, and more.
Want to Help?
Want to report a bug, contribute some code, or improve the documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues labeled as help wanted or good first issue.
Code of Conduct
Help us keep Angular open and inclusive. Please read and follow our Code of Conduct.
Community
Join the conversation and help the community.
- X (formerly Twitter)
- Discord
- Gitter
- YouTube
- StackOverflow
- Find a Local Meetup
Love Angular? Give our repo a star ⭐ ⬆️.