| commit | 6cbd5c4517854fd19536a16191ef332350e7a64d | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Mon Aug 11 06:39:54 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 11 06:39:54 2025 -0700 |
| tree | f3e0f13c48e19aa9656f8d1a4cd12f2bb5d62a9a | |
| parent | 700b784ac20bd66097f56aa970b3d472ce7f8314 [diff] |
[analyzer/linter] Clean up error message comments. This change modifies the comments in the analyzer and linter `messages.yaml` files so that: - Parameters are always described at the end of the comment. If the message takes no parameters, the comment ends with the text `No parameters.` - Parameter descriptions are always word wrapped to 80 columns. It also fixes the format of the comment field for `ANALYSIS_OPTION_DEPRECATED` to remove an unintentional blank line, and adds documentation for the second parameter of `INVALID_EXPORT_OF_INTERNAL_ELEMENT_INDIRECTLY` (which was previously missing). In a follow-up CL, I will transition to a more structured format for parameters in these `messages.yaml` files, and the `Parameters:` sections of the comments will be automatically generated from this structured format during code generation. Cleaning up the comments now will ensure that the follow-up CL is clean (makes no changes to generated files), so we'll be able to have high confidence in its correctness. Change-Id: I6aa1f75fa0b8e4fb9724dcba00fb7d1f06dfb355 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/444205 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Phil Quitslund <pquitslund@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.