Add IntegerTypedArray type for use with crypto.getRandomValues #61767
Conversation
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
typescript-bot
added
the
For Uncommitted Bug
|
This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise. |
1 similar comment
|
This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #61768
Towards microsoft/TypeScript-DOM-lib-generator#1194
The current DOM types
<T extends ArrayBufferView | null>are wrong forcrypto.getRandomValues.nullis never accepted, andArrayBufferViewis too broad as float arrays also aren't accepted.However, fixing in
TypeScript-DOM-lib-generatorrequires conditional inclusion ofBigInt64Array | BigUint64Arraydepending on ES2020 availability. I don't think there's a way to fix that withinTypeScript-DOM-lib-generatorwithout this upstream change inTypeScript.