refactor: eliminate 'any' type in cdk coercion utilities#32889
Closed
jamOne- wants to merge 1 commit intoangular:mainfrom
Closed
refactor: eliminate 'any' type in cdk coercion utilities#32889jamOne- wants to merge 1 commit intoangular:mainfrom
jamOne- wants to merge 1 commit intoangular:mainfrom
Conversation
jamOne-
force-pushed
the
refactor/type-safety/batch-001-cdk-coercion
branch
from
7e3a425 to
ff2107f
Compare
Contributor
|
This draft PR is being closed because it has been stale for 28 days and has seen no activity from you. If you'd like to see this change land, you can re-open this PR. Thank you for being an Angular contributor! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
String(foo)vs${foo}: change is required because TypeScript doesn't allow implicit string coercion in template literals (like${foo}) when the type isunknown. UsingString(foo)behaves exactly the same way at runtime but explicitly tells the TypeScript compiler that the conversion is intentional and safe.