Skip to content

🤖 User test baselines have changed #24952

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
merged 1 commit into from
Jun 14, 2018

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 @mhegazy

@@ -34,9 +34,9 @@ node_modules/chrome-devtools-frontend/front_end/Runtime.js(398,24): error TS8024
node_modules/chrome-devtools-frontend/front_end/Runtime.js(527,49): error TS2352: Type 'Window' cannot be converted to type 'Function'.
Property 'apply' is missing in type 'Window'.
node_modules/chrome-devtools-frontend/front_end/Runtime.js(539,20): error TS2351: Cannot use 'new' with an expression whose type lacks a call or construct signature.
node_modules/chrome-devtools-frontend/front_end/Runtime.js(693,7): error TS2322: Type 'Promise<boolean>' is not assignable to type 'Promise<undefined>'.
node_modules/chrome-devtools-frontend/front_end/Runtime.js(693,7): error TS2322: Type 'Promise<boolean>' is not assignable to type 'Promise<undefined>'.
Copy link
Member

Choose a reason for hiding this comment

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

looks like we still have some duplicate errors. Fix is up at #24508

Copy link
Member

@sandersn sandersn left a comment

Choose a reason for hiding this comment

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

The changes are twofold:

  1. Random order changes from duplicate errors that will be fixed by Fix duplicate errors in js special assignments #24508.
  2. More errors from understanding @this (but still not resolving some types correctly).

@@ -18,6 +18,7 @@ lib/ElementHandle.js(24,15): error TS2503: Cannot find namespace 'Protocol'.
lib/ElementHandle.js(83,29): error TS2503: Cannot find namespace 'Protocol'.
lib/EmulationManager.js(36,16): error TS2503: Cannot find namespace 'Protocol'.
lib/ExecutionContext.js(22,15): error TS2503: Cannot find namespace 'Protocol'.
lib/ExecutionContext.js(87,15): error TS2304: Cannot find name 'Frame'.
Copy link
Member

Choose a reason for hiding this comment

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

this error occurs because we now support @this.

@@ -3245,8 +3245,11 @@ node_modules/chrome-devtools-frontend/front_end/bindings/ResourceScriptMapping.j
node_modules/chrome-devtools-frontend/front_end/bindings/ResourceScriptMapping.js(298,22): error TS2694: Namespace 'Common' has no exported member 'Event'.
node_modules/chrome-devtools-frontend/front_end/bindings/ResourceScriptMapping.js(305,22): error TS2694: Namespace 'Common' has no exported member 'Event'.
node_modules/chrome-devtools-frontend/front_end/bindings/ResourceScriptMapping.js(318,26): error TS2694: Namespace 'Protocol' has no exported member 'Runtime'.
node_modules/chrome-devtools-frontend/front_end/bindings/ResourceScriptMapping.js(323,14): error TS2339: Property '_scriptSource' does not exist on type 'ResourceScriptFile'.
Copy link
Member

Choose a reason for hiding this comment

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

this is now typed, but we can't resolve the properties on the type (it may be incorrect).

@sandersn sandersn merged commit 374cbd6 into microsoft:master Jun 14, 2018
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

2 participants