Repository navigation
In JS, cross-file non-expando assignment declarations are broken #26875
Description
From chrome-devtools-frontend (found in #26861)
// @Filename: file1.js
var N = {}
N.commands = {}
// @Filename: file2.js
N.commands.a = 111
N.commands.b = function () { }Expected behavior:
N.commands.a = 111 is a legal assignment declaration and references to N.commands.a have type number.
Actual behavior:
Both N.commands.a = 111 and references to N.commands.a say that "'a' is not found on 'commands'". N.commands.b is fine, though.
Very likely a result of the change to expando marking.
Activity
sandersn commentedon Sep 4, 2018
This is not a 3.1 regression. It repros in 3.0 too.
Correction: There is no error in 3.0, although the type of 'a' is 'any'.
sandersn commentedon Sep 4, 2018
Completion is also hilariously broken. It suggests
N.commands.N.N.N.N.N.N, although it gives the error "Ndoes not exist ontypeof commands".