tree 31c4580f023792d9fb3d8372b9e93e125793a787
parent de3cec3a470951b9449f231f61284c5b4b123df5
author Konstantin Shcheglov <scheglov@google.com> 1652278604 +0000
committer Commit Bot <commit-bot@chromium.org> 1652278604 +0000

Use 'parsedUnit' of the file as a starting point for the completion.

When we start identifying this synthetic `FieldDeclaration` with code `fo;`
as something that needs resolution (actually enclosing nodes require
declared elements), and use this `FieldDeclaration` as a starting point to
find the `CompletionTarget.entity`, we find the `VariableDeclaration` `fo`.
But if we start with `CompilationUnit` (as we used to), we find
`FieldDeclaration` `fo;`. Which gives different starting points for
contributors, and changes the resulting suggestions.

So, for  now I will switch to using the whole parsed unit.

Change-Id: I153ae4de9faad2f8147f413b36dd8f2dd7bc5a6c
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/244380
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>