| commit | e6228e34cab822bb2b8b629b4362f9450d8c575d | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Tue Dec 09 11:56:11 2025 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 09 11:56:11 2025 -0800 |
| tree | 1f465912c9b4d2cf9687898062de39527d803e0b | |
| parent | d0b5024e40f6f2d08a21e8ab247f2a1b546d5155 [diff] |
[messages] Handle camelCase-formatted files. Updates the logic in `pkg/analyzer_utilities` and `pkg/front_end/test/messages_suite.dart` for processing `messages.yaml` files so that: - Message keys in analyzer-style `messages.yaml` files can be `camelCase`, `lower_snake_case`, or `UPPER_SNAKE_CASE` (previously they could only be `lower_snake_case` or `UPPER_SNAKE_CASE`). - Message keys in CFE-style `messages.yaml` files can be either `camelCase` or `PascalCase` (previously they could only be `PascalCase`). - `sharedName` fields can be `camelCase`, `lower_snake_case`, or `UPPER_SNAKE_CASE` (previously they could only be `lower_snake_case` or `UPPER_SNAKE_CASE`). - `analyzerCode` fields in `pkg/_fe_analyzer_shared/messages.yaml` can be `ClassName.lower_snake_case`, `ClassName.UPPER_SNAKE_CASE`, or `camelCase`, where `ClassName` is ignored (previously they could only be `ClassName.lower_snake_case` or `ClassName.UPPER_SNAKE_CASE`). This paves the way for a follow-up CL in which all these fields and keys will be standardized to `camelCase`, and then the ability to specify them in `lower_snake_case` or `UPPER_SNAKE_CASE` will be removed. This will eliminate a significant inconsistency between the diagnostic code formats in the analyzer and the front end. Note that a few diagnostic names contain an underscore immediately followed by a digit in their snake case representation: - `final_not_initialized_constructor_1` - `final_not_initialized_constructor_2` - `final_not_initialized_constructor_3_plus` - `lines_longer_than_80_chars` When these are converted to `camelCase` form, the code generator will no longer know to introduce the underscores when converting them back to `snake_case` form (e.g. `finalNotInitializedConstructor1` will get converted to `final_not_initialized_constructor1`). The snake case forms are an important part of the customer facing API (since they are what is accepted in `// ignore:` comments), so in order to preserve the existing snake case names, a hardcoded map is introduced, `_snakeCaseExceptions`. Change-Id: I6a6a696444ccd92dd6574a7cde08da88ac5a7135 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/466540 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Paul Berry <paulberry@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.