Paul Berry
46f62c8f69
Adds the getters `lowerCaseName` and `lowerCaseUniqueName` to the `DiagnosticCode` class. These getters behave the same as the `name` and `uniqueName` getters, except that they convert the string to lower case before returning. These getters should help make it easier for the analyzer and related packages (as well as analyzer clients) to treat diagnostic codes in a case-insensitive fashion. In follow-up CLs, I plan to switch the analyzer and related packages over to using the new getters, and then I'll deprecate and eventually remove `name` and `uniqueName` from the analyzer public API. Change-Id: I6a6a6964e8891fc6f74a9777eae375f1a553c2f3 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/466182 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Paul Berry <paulberry@google.com>
SDK development code analysis
dartanalyzer used to be the tool for statically analyzing dart code
at the command line. However, this tool has been replaced with
dart analyze for this purpose in current SDKs and will no longer
be published on pub.
Do not depend on the command line interface or other semantics in
this directory as it is now an internal tool for SDK development, used
as the dart2analyzer "compiler" for tools/test.py in the SDK.
It is configured as part of the test runner,
here.
SDK development usage
For SDK development, run analysis from the test tool to validate analysis conclusions on language samples in the testing directory. From the root of the SDK:
tools/test.py --build --use-sdk -c dart2analyzer co19 language
This will build the Dart VM and compile dartanalyzer into a snapshot, then use
that snapshot while analyzing those directories under testing/. Without
--use-sdk, test.py will use the source code version of the analyzer
instead of the compiled one, which can be useful for debugging.