docs(faq): Mention TypeScript 3’s unknown type
#1290
Merged
Conversation
This file contains 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
ExE-Boss
force-pushed
the
docs/faq/typescript3-unknown-type
branch
from
ed5c1db to
630be38
Compare
Signed-off-by: ExE Boss <[email protected]>
|
@ExE-Boss Thank you very much for the contribution. And you are absolutely right. |
jpilgrim
approved these changes
Apr 3, 2019
|
@mor-n4 Would it be ok for you to merge this PR? |
|
Yes, good to mention this in the docs for completeness! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TypeScript 3 added the
unknowntype, which behaves like N4JS’sanytype.See also microsoft/TypeScript#27265, which would add a compiler flag to TypeScript that would switch the implicit type from
anytounknown.