Konstantin Shcheglov
921ec7f507
Replace the positional Scanner constructors with a single constructor that takes the input text and error reporting callback as named required arguments. Remove the unused fasta forwarding constructor, reader offset handling, and stored first token. The scanner now keeps only the input text and returns the token stream directly from tokenize. Update analyzer, analysis server, plugin, CLI, scrape, and scanner test call sites to use the named constructor arguments. Change-Id: Ieabb7b28570d4a963563fb2d1c5ef5ac0c89032a Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/500340 Reviewed-by: Johnni Winther <johnniwinther@google.com> Reviewed-by: Bob Nystrom <rnystrom@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Paul Berry <paulberry@google.com>
analysis_server_plugin package
This package offers support for writing Dart analysis server plugins, for Dart 3.10 (Flutter 3.38) and later.
Analysis server plugins empower developers to contribute their own Dart static
analysis in IDEs and at the command line via dart analyze and flutter analyze. Analysis server plugins can offer the following static analyses:
- analysis rules, which report diagnostics in the IDE, and at the command line
- IDE quick fixes, which are local refactorings offered to users to correct a given diagnostic
- IDE quick assists, which are local refactorings that are offered at specific syntax nodes in code, but do not necessarily correct a static code issue
Review the following documents for how to write and how to use analysis server plugins: