Handle parentless nodes in isParameterPropertyDeclaration #33321
+64
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #33295.
This follows a similar pattern as in #20314 by requiring an explicit
parent
parameter. Where possible, it uses the appopriate variable atthe call sites.
In several locations there is no context available though (e.g.
inspecting
valueDeclarations
) and we access.parent
as the codepreviously did. From a cursory inspection this seems correct, these
callpaths originate in phases where there must be a
parent
(i.e. inchecker, binder, etc).
Change-Id: I28e4726777b57237bec776e4001e9e69ac591b11