Skip to content

Revert "Better typings for Promise.resolve(), like #31117 (#33074)" - #50227

Closed
Nathan Shively-Sanders (sandersn) wants to merge 1 commit into
mainfrom
revert-33074
Closed

Revert "Better typings for Promise.resolve(), like #31117 (#33074)"#50227
Nathan Shively-Sanders (sandersn) wants to merge 1 commit into
mainfrom
revert-33074

Conversation

@sandersn

Copy link
Copy Markdown
Member

This reverts commit 040c121.

#33074 (comment)

@DanielRosenwasser

Copy link
Copy Markdown
Member

TypeScript Bot (@typescript-bot) cherry-pick this to release-4.8

@typescript-bot

TypeScript Bot (typescript-bot) commented Aug 9, 2022

Copy link
Copy Markdown
Contributor

Heya Daniel Rosenwasser (@DanielRosenwasser), I've started to run the task to cherry-pick this into release-4.8 on this PR at c28ee65. You can monitor the build here.

@typescript-bot

Copy link
Copy Markdown
Contributor

Hey Daniel Rosenwasser (@DanielRosenwasser), I've opened #50229 for you.

TypeScript Bot (typescript-bot) pushed a commit to typescript-bot/TypeScript that referenced this pull request Aug 9, 2022
Component commits:
c28ee65 Revert "Better typings for Promise.resolve(), like microsoft#31117 (microsoft#33074)"
This reverts commit 040c121.
TypeScript Bot (typescript-bot) pushed a commit to typescript-bot/TypeScript that referenced this pull request Aug 11, 2022
Component commits:
c28ee65 Revert "Better typings for Promise.resolve(), like microsoft#31117 (microsoft#33074)"
This reverts commit 040c121.

Co-authored-by: Nathan Shively-Sanders <nathansa@microsoft.com>
@sandersn

Copy link
Copy Markdown
Member Author

Having reviewed the vs code and DT failures, I think the original change is good, and should ship in 4.9 now that vscode updated to avoid the compile errors. I'll close this PR.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants