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
fix(core): adjust toSignal types to handle more common cases #51991
Conversation
Marking it as cleanup since it needs the public API update |
bbd78ff
to
84248fa
Compare
This commit cleans up the signatures of `toSignal` to better handle the types of situations that it might be used in, and produce better type inference results. Fixes angular#50687 Fixes angular#50591 Co-authored-by: Andrew Scott <atscott@google.com>
84248fa
to
a7f067f
Compare
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.
LGTM
Reviewed-for: public-api
Reviewed-for: fw-core
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
This PR was merged into the repository by commit 5411864. |
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. |
…#51991) This commit cleans up the signatures of `toSignal` to better handle the types of situations that it might be used in, and produce better type inference results. Fixes angular#50687 Fixes angular#50591 Co-authored-by: Andrew Scott <atscott@google.com> PR Close angular#51991
This commit cleans up the signatures of
toSignal
to better handle the types of situations that it might be used in, and produce better type inference results.Fixes #50687
Fixes #50591