Skip to content
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

feat: update to TypeScript 4.7 #14242

Merged
merged 8 commits into from
Jun 1, 2022
Merged

feat: update to TypeScript 4.7 #14242

merged 8 commits into from
Jun 1, 2022

Conversation

kitsonk
Copy link
Contributor

@kitsonk kitsonk commented Apr 9, 2022

No description provided.

@@ -7,10 +7,6 @@

/// <reference no-default-lib="true"/>

interface AbortSignal extends EventTarget {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is now part of lib dom.

// code_actions: Option<Vec<CodeAction>>,
// source: Option<Vec<SymbolDisplayPart>>,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is deprecated, so we shouldn't ever use it if we need it.

@kitsonk kitsonk changed the title [WIP] feat: update to TypeScript 4.7 feat: update to TypeScript 4.7 May 31, 2022
@kitsonk kitsonk marked this pull request as ready for review May 31, 2022 01:32
Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, should we wait until the week of June 13th before landing this PR? It appears it might be painful to not apply it in v1.22 branch

@@ -695,7 +723,7 @@ interface AbortController {
/** Returns the AbortSignal object associated with this object. */
readonly signal: AbortSignal;
/** Invoking this method will set this object's AbortSignal's aborted flag and signal to any observers that the associated activity is to be aborted. */
abort(reason?: any): void;
// abort(): AbortSignal; - To be re-added in the future
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this on purpose? Looks strange

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, this seems a bit problematic.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is what is upstream: https://github.com/microsoft/TypeScript/blob/release-4.7/lib/lib.webworker.d.ts#L726

I really don't want to get into updating their distributables if we can avoid it. It appears they have fixed it in main, but that is what they issued with 4.7. The impact on Deno users will be minimal, because it only gets used when users explicitly use it.

Copy link
Member

@dsherret dsherret left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM too

@kitsonk
Copy link
Contributor Author

kitsonk commented May 31, 2022

LGTM, should we wait until the week of June 13th before landing this PR? It appears it might be painful to not apply it in v1.22 branch

I would rather get it in so canary has it so it isn't some big surprise when it makes the release as it may highlight more "breakages" in std and in other libraries.

It is mostly atomic except for the LSP changes, and even then, it is stuff we likely won't be touching anytime soon.

Also, I am away the week of June 13th.

@bartlomieju
Copy link
Member

LGTM, should we wait until the week of June 13th before landing this PR? It appears it might be painful to not apply it in v1.22 branch

I would rather get it in so canary has it so it isn't some big surprise when it makes the release as it may highlight more "breakages" in std and in other libraries.

It is mostly atomic except for the LSP changes, and even then, it is stuff we likely won't be touching anytime soon.

Also, I am away the week of June 13th.

Okay, let's land it now then. I'll cut the 1.23.2 release and deal with any troubles then.

@kitsonk kitsonk merged commit 7eee521 into denoland:main Jun 1, 2022
@kitsonk kitsonk deleted the ts_47 branch June 1, 2022 00:19
bartlomieju pushed a commit that referenced this pull request Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants