[core] Precise Typechecking #32099
Merged
[core] Precise Typechecking #32099
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
|
API change check API changes are not detected in this pull request. |
deyaaeldeen
force-pushed
the
core-precise-typechecking
branch
4 times, most recently
from
b378bff to
6e144fb
Compare
deyaaeldeen
force-pushed
the
core-precise-typechecking
branch
from
6e144fb to
6c69f2d
Compare
deyaaeldeen
requested review from
a team,
jeremymeng,
maorleger,
mpodwysocki,
joheredi,
timovv,
HarshaNalluru and
xirzec
as code owners
jeremymeng
reviewed
Dec 9, 2024
mpodwysocki
reviewed
Dec 9, 2024
jeremymeng
reviewed
Dec 9, 2024
jeremymeng
approved these changes
Dec 9, 2024
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.
For core:
integration-test:nodecommand that targets the esm build