| commit | 85227c449265527783b077a55696da202168a5b8 | [log] [tgz] |
|---|---|---|
| author | Ben Konyi <bkonyi@google.com> | Thu Apr 24 11:15:59 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 24 11:15:59 2025 -0700 |
| tree | 19e83d0433a3dc7b39e90c332c8b451732b14f94 | |
| parent | f7ff419cd36da46855b22fdfbad557b7385ef61b [diff] |
[ 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>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.