-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Update TypeScript DOM Libs #47445
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
Update TypeScript DOM Libs #47445
Conversation
3649604
to
903cb75
Compare
@typescript-bot test this |
This looks like it won't break much, IMO |
@typescript-bot run dt |
@@ -1873,7 +1885,7 @@ interface AbortSignal extends EventTarget { | |||
declare var AbortSignal: { | |||
prototype: AbortSignal; | |||
new(): AbortSignal; | |||
// abort(): AbortSignal; - To be re-added in the future | |||
abort(reason?: any): AbortSignal; |
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.
This I thought was a part of the automation, but I guess not - might have to change it on the DOM side
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.
You mean we might need to add an override?
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.
Nah, this was not supposed to happen because it conflicts with the node AbortSignal - but the deploy process didn't take into account the new param - microsoft/TypeScript-DOM-lib-generator@1bba426
@@ -4928,8 +4943,10 @@ interface EventSource extends EventTarget { | |||
readonly CONNECTING: number; | |||
readonly OPEN: number; | |||
addEventListener<K extends keyof EventSourceEventMap>(type: K, listener: (this: EventSource, ev: EventSourceEventMap[K]) => any, options?: boolean | AddEventListenerOptions): void; | |||
addEventListener(type: string, listener: (this: EventSource, event: MessageEvent) => any, options?: boolean | AddEventListenerOptions): void; |
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.
What's the rationale for these new overloads?
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.
microsoft/TypeScript-DOM-lib-generator#736 with microsoft/TypeScript-DOM-lib-generator#1182 - basically default to message event if we don't know the event name
Going to merge this for now for the beta, but I still feel a little confused about those 2 changes. |
This PR was generated by @orta from https://github.com/microsoft/TypeScript-DOM-lib-generator/