-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Ensure file, include and exclude specs used are strings #40041
Conversation
@typescript-bot test this |
Heya @DanielRosenwasser, I've started to run the extended test suite on this PR at 959dee4. You can monitor the build here. |
Heya @DanielRosenwasser, I've started to run the parallelized Definitely Typed test suite on this PR at 959dee4. You can monitor the build here. |
Heya @DanielRosenwasser, I've started to run the parallelized community code test suite on this PR at 959dee4. You can monitor the build here. |
@typescript cherry-pick this to release-4.0 and LKG |
The user suite test run you requested has finished and failed. I've opened a PR with the baseline diff from master. |
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.
The fix looks right, but the return type is awfully hard to read. I have a straw-man suggestion for making it explicit.
dd424d9
to
9d9f7e4
Compare
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.
Looks good; one question about what to return when array elements have the wrong type.
@typescript cherry-pick this to release-4.0 and LKG |
@typescript-bot cherry-pick this to release-4.0 and LKG |
@sheetalkamat #39856 is still open but should be fixed by this PR. |
Thanks closed it |
Fixes #38164, #39856