You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handle parentless nodes in isParameterPropertyDeclaration
Fixesmicrosoft#33295.
This follows a similar pattern as in microsoft#20314 by requiring an explicit
`parent` parameter. Where possible, it uses the appopriate variable at
the call sites.
In several locations there is no context available though (e.g.
inspecting `valueDeclarations`) and we access `.parent` as the code
previously did. From a cursory inspection this seems correct, these
callpaths originate in phases where there must be a `parent` (i.e. in
checker, binder, etc).
Change-Id: I28e4726777b57237bec776e4001e9e69ac591b11
Debug.assert(paramProps.length===2&&!!(paramProps[0].flags&SymbolFlags.FunctionScopedVariable)&&!!(paramProps[1].flags&SymbolFlags.Property));// is [parameter, property]
0 commit comments