Skip to content

Handle parentless nodes in isParameterPropertyDeclaration - #33472

Merged
Daniel Rosenwasser (DanielRosenwasser) merged 1 commit into
masterfrom
parentNodesPortMaster
Sep 17, 2019
Merged

Daniel Rosenwasser (DanielRosenwasser) merged 1 commit into
masterfrom
parentNodesPortMaster

Conversation

@DanielRosenwasser

Copy link
Copy Markdown
Member

Ports #33321 into master, fixes #33295.

Fixes #33295.

This follows a similar pattern as in #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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Regression: 3.6 crashes if constructor parameters transformed

3 participants