You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally we should determine when a deprecated overload is being called. If that is not possible right now, I think we should be conservative and only mark a call deprecated if all of its overloads are deprecated
Using 4.0.0-dev20200708 I see deprecation warnings as below. Not sure if this isn't the latest release (tho using ms-vscode.vscode-typescript-next) or if this is the same as the createElement-issue.
Using 4.0.0-dev20200708 I see deprecation warnings as below. Not sure if this isn't the latest release (tho using ms-vscode.vscode-typescript-next) or if this is the same as the createElement-issue.
(same with 20200712)
It's already fixed in nightly build yesterday(utc+8, or today)
You can see #39590
Activity
mjbvz commentedon Jun 23, 2020
Ideally we should determine when a deprecated overload is being called. If that is not possible right now, I think we should be conservative and only mark a call deprecated if all of its overloads are deprecated
Kingwl commentedon Jun 24, 2020
Okay, I'll take a look soon.
jrieken commentedon Jul 16, 2020
Using 4.0.0-dev20200708 I see deprecation warnings as below. Not sure if this isn't the latest release (tho using
ms-vscode.vscode-typescript-next) or if this is the same as the createElement-issue.(same with 20200712)
Kingwl commentedon Jul 16, 2020
It's already fixed in nightly build yesterday(utc+8, or today)
You can see #39590