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
Instantiate native promise instead of WinJS.Promise #62716
Comments
Started this but need to wait until lower level stuff like |
Did:
@alexr00 can you do |
Using
As long as you check that the code will be safe when the upstream method switches from TPromise to Promise. |
Yes, there are three ways to deal with not-yet-converted dependencies (and I think that 1 and 2 are the best ways to tackle this)
|
Makes sense. Since the |
Completed my set:
Words of warning for @Microsoft/vscode: since this touched both the old tree as well as |
@bpasero Why the reassign? Are there more files I should look at? I've done the files under my name. |
@alexandrudima sorry I thought people would remove the ones that are done from the summary like Joao did. |
Had to revert the one in |
Ah whatever, converted the last one 💯 |
awesome! |
This is part of #53526 and points out files in which we call
new WinJS.Promise
. In addition tojoin
,as
,wrap
, andwrapError
that's how winjs promises end up in our system and we wanna get rid of them.Please migrate to instantiating native promises with taking all care that's needed for this adoption.
@bpasero
src/vs/platform/lifecycle/electron-main/lifecycleMain.ts
The text was updated successfully, but these errors were encountered: