-
Notifications
You must be signed in to change notification settings - Fork 27k
feat(core): add Angular Signals to the public API #49150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
dylhunn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reviewed-for: fw-core, public-api
AndrewKushnir
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed-for: public-api
|
I'm excited to see Angular's signal land as public API, thanks for the work on the developer Preview ❤️ |
|
Caretaker: this will need a new g3 patch. |
jessicajaniuk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reviewed-for: public-api
54d1608 to
af397e3
Compare
af397e3 to
dc75079
Compare
This commit exposes `signal`, `computed`, `effect` and various helpers from the `@angular/core` entrypoint. These APIs are marked as `@developerPreview` and are still prototypes in active development. Their final shapes will be subject to our internal design reviews as well as one or more community RFCs. We're exporting them now to allow for experimentation using 16.0.0 next and RC releases.
dc75079 to
874a540
Compare
|
This PR was merged into the repository by commit bc5ddab. |
|
I miss the old days of the aesthetically pleasing and readable syntax of ref() in Vue and useState() in React for reactive synchronous values. It's inspiring to see how these three frameworks and libraries have influenced and inspired each other. I cannot wait to see these features publicly released! Kudos to you guys who are behind all of these amazing features. |
|
If we don't preprocess function in |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
For context, see this Github Discussion on our experiments with fine-grained reactivity in Angular
This commit exposes
signal,computed,effectand various helpers from the@angular/coreentrypoint.These APIs are marked as
@developerPreviewand are still prototypes in active development. Their final shapes will be subject to our internal design reviews as well as one or more community RFCs. We're exporting them now to allow for experimentation using 16.0.0 next and RC releases.