-
Notifications
You must be signed in to change notification settings - Fork 13k
Add type definitions for Uint8Array
to/from base64 methods
#61696
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
This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise. |
@microsoft-github-policy-service agree |
Officially shipped in Chrome 140 |
This PR needs a merge from main in order to be mergable. |
This all seems fine, but, double checking: @typescript-bot test it |
Hey @jakebailey, the results of running the DT tests are ready. Everything looks the same! |
@jakebailey Here are the results of running the user tests with tsc comparing There were infrastructure failures potentially unrelated to your change:
Otherwise... Everything looks good! |
@jakebailey Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
@jakebailey Here are the results of running the top 400 repos with tsc comparing Everything looks good! |
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.
Sorry, I missed something here; the options bags need to have explicit | undefined
annotation in addition to ?
to indicate that passing an explicit undefined is okay (versus requiring it be "missing").
Hopefully this is better. Thank you for taking the time to review the changes. |
FWIW we don't usually make tests for |
I see. Should I? Out of curiosity, what is the 'cases/conformance/esnext' directory for (in that case)? |
It used to be for emit, but I think I missed the added test for Atomic in #61646. |
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 but need to double check that the extra file is the right solution.
Going to just take this as-is. When they are in ES2025 (or later?), these files will get deleted anyway (see also #58573). |
See #61695, which this pull request attempts to fix
Fixes #61695