| commit | 2b5b3163e6b92b553ca02d49f762c7289c66aec1 | [log] [tgz] |
|---|---|---|
| author | Jens Johansen <jensj@google.com> | Fri Dec 13 05:37:29 2024 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 13 05:37:29 2024 -0800 |
| tree | c4e52782084a5b50adba72fb875c8056b6552729 | |
| parent | 555d9ea9c31fa6c7815cd0c7e2a775c9b71f6883 [diff] |
[status_file] Status file linting should not check for non-existing files when given input on stdin Given input on stdin it has no path to resolve the relative paths that exists in a status file from. It will thus complain about almost all lines which is not ideal. This CL changes it so it doesn't check for it when given data on stdin. This also means that - because there are no old errors on that account - if there are such errors now you will be forced to fix it. The current errors in the status files I could find have also been fixed. This should for instance have flaggen when I in https://dart-review.googlesource.com/c/sdk/+/400320 updated the pkg.status file but forgot to actually rename the underlying file (as fixed in https://dart-review.googlesource.com/c/sdk/+/400560). Technically I suppose it _did_ flag it, but there were also hundreds of lines of false positives caused by the old status file been given at stdin to check if there were existing errors - which there then was, thus not forcing me to do anything. Logical follow-up to https://dart-review.googlesource.com/c/sdk/+/370886 TEST=ci Change-Id: Ib3533ede88b6d99a31f8b423c00930857e0ba49f Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/400620 Reviewed-by: Alexander Thomas <athom@google.com> Commit-Queue: Jens Johansen <jensj@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.