tree 19e83d0433a3dc7b39e90c332c8b451732b14f94
parent f7ff419cd36da46855b22fdfbad557b7385ef61b
author Ben Konyi <bkonyi@google.com> 1745518559 -0700
committer Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> 1745518559 -0700

[ Analyzer ] Add diagnostics for Flutter Widget Previews

The Flutter Widget Previewer relies on code generation to import code from
a developer's project into a generated 'widget preview scaffold' that lives
in the project's '.dart_tool' directory. The nature of this implementation
means that any symbols referenced in the declaration of the preview (e.g.,
in the invocation of the `Preview(...)` constructor or the name of the
preview function) must be publicly accessible from outside the library in
which they are defined. One of the main uses for this diagnostic is to flag
usages of private symbols within preview declarations.

These diagnostics also ensures that the `@Preview(...)` annotation can only be
applied to a functions or constructors that:

  - Are statically accessible (e.g., no instance methods)
  - Have explicit implementations (e.g., not abstract or external)

Fixes https://github.com/flutter/flutter/issues/167193

Change-Id: I208c7f18c8d4ad826fed46a0dc625d090ff186ef
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/423860
Commit-Queue: Ben Konyi <bkonyi@google.com>
Reviewed-by: Paul Berry <paulberry@google.com>
Auto-Submit: Ben Konyi <bkonyi@google.com>
Reviewed-by: Samuel Rawlins <srawlins@google.com>