Skip to content

🤖 User test baselines have changed #33635

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

Merged

Conversation

typescript-bot
Copy link
Collaborator

Please review the diff and merge if no changes are unexpected.
You can view the build log here.

cc @weswigham @sandersn @RyanCavanaugh

Copy link
Member

@weswigham weswigham left a comment

Choose a reason for hiding this comment

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

I think most of these are expected, though the xterm changes and the new errors in the chrome devtools should be inspected.

Copy link
Member

@weswigham weswigham left a comment

Choose a reason for hiding this comment

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

By and large these look good - I've opened #33641 and #33640 to track this issues in the azure-sdk, though.

Standard output:

> xterm@X.X.X build /xtermjs
> tsc -b ./tsconfig.all.json
src/browser/Clipboard.ts(85,5): error TS2322: Type 'null' is not assignable to type 'string'.
Copy link
Member

Choose a reason for hiding this comment

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

These are due to a DOM update that removed null as a valid type for some members of CSSStyleDeclaration.

@@ -8,7 +8,7 @@ node_modules/bcryptjs/src/bcrypt.js(150,5): error TS2322: Type 'string | undefin
Type 'undefined' is not assignable to type 'string'.
node_modules/bcryptjs/src/bcrypt.js(160,14): error TS2366: Function lacks ending return statement and return type does not include 'undefined'.
node_modules/bcryptjs/src/bcrypt.js(238,14): error TS2366: Function lacks ending return statement and return type does not include 'undefined'.
node_modules/bcryptjs/src/bcrypt/impl.js(516,22): error TS2345: Argument of type 'Int32List' is not assignable to parameter of type 'number[]'.
node_modules/bcryptjs/src/bcrypt/impl.js(516,22): error TS2345: Argument of type 'number[] | Int32Array' is not assignable to parameter of type 'number[]'.
Copy link
Member

Choose a reason for hiding this comment

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

Interesting - we lost an alias here. @sandersn do you know if the type Int32List = Int32Array | GLint[]; alias was removed from dom (and inlined at usages)? That's probably a breaking change.

Type '{ ExpandRetainersComplete: symbol; }' is missing the following properties from type '{ ContentShown: symbol; SortingComplete: symbol; }': ContentShown, SortingComplete
node_modules/chrome-devtools-frontend/front_end/profiler/HeapSnapshotDataGrids.js(603,43): error TS2417: Class static side 'typeof HeapSnapshotRetainmentDataGrid' incorrectly extends base class static side 'typeof HeapSnapshotContainmentDataGrid'.
Types of property 'Events' are incompatible.
Type '{ ExpandRetainersComplete: symbol; }' is not assignable to type '{ ContentShown: symbol; SortingComplete: symbol; }'.
Copy link
Member

Choose a reason for hiding this comment

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

Static side inheritance errors brought on by better usage of getMergeSymbol in the js declaration emitter PR. We should have always been issuing these.

lib/WebSocketTransport.js(32,72): error TS2345: Argument of type 'WebSocket' is not assignable to parameter of type 'WebSocket'.
Property 'dispatchEvent' is missing in type 'WebSocket' but required in type 'WebSocket'.
lib/WebSocketTransport.js(32,72): error TS2345: Argument of type 'import("/puppeteer/puppeteer/node_modules/@types/ws/index")' is not assignable to parameter of type 'WebSocket'.
Property 'dispatchEvent' is missing in type 'import("/puppeteer/puppeteer/node_modules/@types/ws/index")' but required in type 'WebSocket'.
Copy link
Member

Choose a reason for hiding this comment

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

It looks more strange, but now you know that the global WebSocket and the WebSocket referred to on the LHS differ. I'm pretty sure this is just due to some better prioritization in symbols during symbol name lookup (also actually recognizing that a exports = WebSocket means the module symbol is a viable reference to the WebSocket).

@weswigham weswigham merged commit c283809 into microsoft:master Sep 27, 2019
@weswigham
Copy link
Member

cc @DanielRosenwasser at least as-is, 3.7 is going to be breaky for azure-sdk (I imagine we'll have to add another compiler option to opt-out of getter/setter declaration emit). I'm unsure who best to contact about that to keep them informed. Maybe @bterlson?

@bterlson
Copy link
Member

Yes please keep me in the loop!

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.

3 participants